Encoding and decoding information about a motion information predictor

ABSTRACT

A method of encoding information about a motion information predictor, comprising: selecting one of a plurality of motion information predictor candidates; and encoding information for identifying the selected motion information predictor candidate using CABAC coding, wherein the CABAC coding comprises, for at least one bit of said information, using the same context variable used for another inter prediction mode when one or both of a Triangle Merge mode or a Merge with Motion Vector Difference (MMVD) Merge mode is used.

FIELD OF INVENTION

The present invention relates to video coding and decoding.

BACKGROUND

Recently, the Joint Video Experts Team (JVET), a collaborative team formed by MPEG and ITU-T Study Group 16's VCEG, commenced work on a new video coding standard referred to as Versatile Video Coding (VVC). The goal of VVC is to provide significant improvements in compression performance over the existing HEVC standard (i.e., typically twice as much as before) and to be completed in 2020. The main target applications and services include—but not limited to—360-degree and high-dynamic-range (HDR) videos. In total, JVET evaluated responses from 32 organizations using formal subjective tests conducted by independent test labs. Some proposals demonstrated compression efficiency gains of typically 40% or more when compared to using HEVC. Particular effectiveness was shown on ultra-high definition (UHD) video test material. Thus, we may expect compression efficiency gains well-beyond the targeted 50% for the final standard.

The JVET exploration model (JEM) uses all the HEVC tools. A further tool not present in HEVC is to use an ‘affine motion mode’ when applying motion compensation. Motion compensation in HEVC is limited to translations, but in reality there are many kinds of motion, e.g. zoom in/out, rotation, perspective motions and other irregular motions. When utilising affine motion mode, a more complex transform is applied to a block to attempt to more accurately predict such forms of motion. So it would be desirable if the affine motion mode can be used whilst achieving a good coding efficiency but with less complexity.

Another tool not present in HEVC is to use Alternative Temporal Motion Vector Prediction (ATMVP). The alternative temporal motion vector prediction (ATMVP) is a particular motion compensation. Instead of considering only one motion information for the current block from a temporal reference frame, each motion information of each collocated block is considered. So this temporal motion vector prediction gives a segmentation of the current block with the related motion information of each sub-block. In the current VTM (VVC Test Model) reference software, ATMVP is signalled as a merge candidate inserted in the list of Merge candidates. When ATMVP is enabled at SPS level, the maximum number of Merge candidates is increased by one. So 6 candidates are considered instead of 5 from when this mode is disabled.

These, and other tools described later, are bringing up problems relating to the coding efficiency and complexity of the coding of an index (e.g. a Merge index) or a flag used to signal which candidate is selected from among the list of candidates (e.g. from a list of Merge candidates for use with a Merge mode coding).

Accordingly, a solution to at least one of the aforementioned problems is desirable.

According to a first aspect of the present invention there is provided a method of encoding a motion vector predictor index, comprising: generating a list of motion vector predictor candidates including an ATMVP candidate; selecting one of the motion vector predictor candidates in the list; and generating a motion vector predictor index (Merge index) for the selected motion vector predictor candidate using CABAC coding, one or more bits of the motion vector predictor index being bypass CABAC coded. In one embodiment, all bits except for a first bit of the motion vector predictor index are bypass CABAC coded.

According to a second aspect of the present invention there is provided a method of decoding a motion vector predictor index, comprising: generating a list of motion vector predictor candidates including an ATMVP candidate; decoding the motion vector predictor index using CABAC decoding, one or more bits of the motion vector predictor index being bypass CABAC decoded; and using the decoded motion vector predictor index to identify one of the motion vector predictor candidates in the list. In one embodiment, all bits except for a first bit of the motion vector predictor index are bypass CABAC decoded.

According to a third aspect of the present invention there is provided a device for encoding a motion vector predictor index, comprising: means for generating a list of motion vector predictor candidates including an ATMVP candidate; means for selecting one of the motion vector predictor candidates in the list; and means for generating a motion vector predictor index (Merge index) for the selected motion vector predictor candidate using CABAC coding, one or more bits of the motion vector predictor index being bypass CABAC coded.

According to a fourth aspect of the present invention there is provided a device for decoding a motion vector predictor index, comprising: means for generating a list of motion vector predictor candidates including an ATMVP candidate; means for decoding the motion vector predictor index using CABAC decoding, one or more bits of the motion vector predictor index being bypass CABAC decoded; and means for using the decoded motion vector predictor index to identify one of the motion vector predictor candidates in the list.

According to a fifth aspect of the present invention there is provided a method of encoding a motion vector predictor index, comprising: generating a list of motion vector predictor candidates; selecting one of the motion vector predictor candidates in the list; and generating a motion vector predictor index for the selected motion vector predictor candidate using CABAC coding, two or more bits of the motion vector predictor index sharing the same context. In one embodiment, all bits of the motion vector predictor index share the same context.

According to a sixth aspect of the present invention there is provided a method of decoding a motion vector predictor index, comprising: generating a list of motion vector predictor candidates; decoding the motion vector predictor index using CABAC decoding, two or more bits of the motion vector predictor index sharing the same context; and using the decoded motion vector predictor index to identify one of the motion vector predictor candidates in the list. In one embodiment, all bits of the motion vector predictor index share the same context.

According to a seventh aspect of the present invention there is provided a device for encoding a motion vector predictor index, comprising: means for generating a list of motion vector predictor candidates; means for selecting one of the motion vector predictor candidates in the list; and means for generating a motion vector predictor index for the selected motion vector predictor candidate using CABAC coding, two or more bits of the motion vector predictor index sharing the same context.

According to an eighth aspect of the present invention there is provided a device for decoding a motion vector predictor index, comprising: means for generating a list of motion vector predictor candidates; means for decoding the motion vector predictor index using CABAC decoding, two or more bits of the motion vector predictor index sharing the same context; and means for using the decoded motion vector predictor index to identify one of the motion vector predictor candidates in the list.

According to a ninth aspect of the present invention there is provided a method of encoding a motion vector predictor index, comprising: generating a list of motion vector predictor candidates; selecting one of the motion vector predictor candidates in the list; and generating a motion vector predictor index for the selected motion vector predictor candidate using CABAC coding, wherein a context variable for at least one bit of the motion vector predictor index of a current block depends on a motion vector predictor index of at least one block neighbouring the current block. In one embodiment the context variable for at least one bit of the motion vector predictor index depends on the respective motion vector predictor indexes of at least two neighbouring blocks. In another embodiment the context variable for at least one bit of the motion vector predictor index depends on a motion vector predictor index of a left neighbouring block on the left of the current block and on a motion vector predictor index of an upper neighbouring block above the current block. In another embodiment the left neighbouring block is A2 and the upper neighbouring block is B3. In another embodiment the left neighbouring block is A1 and the upper neighbouring block is B1. In another embodiment the context variable has 3 different possible values. Another embodiment comprises comparing the motion vector predictor index of at least one neighbouring block with an index value of the motion vector predictor index of the current block and setting said context variable in dependence upon the comparison result. Another embodiment comprises comparing the motion vector predictor index of at least one neighbouring block with a parameter representing a bit position of the or one said bit in the motion vector predictor index of the current block and setting said context variable in dependence upon the comparison result. Yet another embodiment comprises: making a first comparison, comparing the motion vector predictor index of a first neighbouring block with a parameter representing a bit position of the or one said bit in the motion vector predictor index of the current block; making a second comparison, comparing the motion vector predictor index of a second neighbouring block with said parameter; and setting said context variable in dependence upon the results of the first and second comparisons.

According to a tenth aspect of the present invention there is provided a method of decoding a motion vector predictor index, comprising: generating a list of motion vector predictor candidates; decoding the motion vector predictor index using CABAC decoding, wherein a context variable for at least one bit of the motion vector predictor index of a current block depends on a motion vector predictor index of at least one block neighbouring the current block; and using the decoded motion vector predictor index to identify one of the motion vector predictor candidates in the list. In one embodiment the context variable for at least one bit of the motion vector predictor index depends on the respective motion vector predictor indexes of at least two neighbouring blocks. In another embodiment the context variable for at least one bit of the motion vector predictor index depends on a motion vector predictor index of a left neighbouring block on the left of the current block and on a motion vector predictor index of an upper neighbouring block above the current block. In another embodiment the left neighbouring block is A2 and the upper neighbouring block is B3. In another embodiment the left neighbouring block is A1 and the upper neighbouring block is B1. In another embodiment the context variable has 3 different possible values. Another embodiment comprises comparing the motion vector predictor index of at least one neighbouring block with an index value of the motion vector predictor index of the current block and setting said context variable in dependence upon the comparison result. Another embodiment comprises comparing the motion vector predictor index of at least one neighbouring block with a parameter representing a bit position of the or one said bit in the motion vector predictor index of the current block and setting said context variable in dependence upon the comparison result. Yet another embodiment comprises: making a first comparison, comparing the motion vector predictor index of a first neighbouring block with a parameter representing a bit position of the or one said bit in the motion vector predictor index of the current block; making a second comparison, comparing the motion vector predictor index of a second neighbouring block with said parameter; and setting said context variable in dependence upon the results of the first and second comparisons.

According to an eleventh aspect of the present invention there is provided a device for encoding a motion vector predictor index, comprising: means for generating a list of motion vector predictor candidates; means for selecting one of the motion vector predictor candidates in the list; and means for generating a motion vector predictor index for the selected motion vector predictor candidate using CABAC coding, wherein a context variable for at least one bit of the motion vector predictor index of a current block depends on a motion vector predictor index of at least one block neighbouring the current block.

According to a twelfth aspect of the present invention there is provided a device for decoding a motion vector predictor index, comprising: means for generating a list of motion vector predictor candidates; means for decoding the motion vector predictor index using CABAC decoding, wherein a context variable for at least one bit of the motion vector predictor index of a current block depends on a motion vector predictor index of at least one block neighbouring the current block; and means for using the decoded motion vector predictor index to identify one of the motion vector predictor candidates in the list.

According to a thirteenth aspect of the present invention there is provided a method of encoding a motion vector predictor index, comprising: generating a list of motion vector predictor candidates; selecting one of the motion vector predictor candidates in the list; and generating a motion vector predictor index for the selected motion vector predictor candidate using CABAC coding, wherein a context variable for at least one bit of the motion vector predictor index of a current block depends on a Skip flag of said current block.

According to a fourteenth aspect of the present invention there is provided a method of encoding a motion vector predictor index, comprising: generating a list of motion vector predictor candidates; selecting one of the motion vector predictor candidates in the list; and generating a motion vector predictor index for the selected motion vector predictor candidate using CABAC coding, wherein a context variable for at least one bit of the motion vector predictor index of a current block depends on another parameter or syntax element of said current block that is available prior to decoding of the motion vector predictor index.

According to a fifteenth aspect of the present invention there is provided a method of encoding a motion vector predictor index, comprising: generating a list of motion vector predictor candidates; selecting one of the motion vector predictor candidates in the list; and generating a motion vector predictor index for the selected motion vector predictor candidate using CABAC coding, wherein a context variable for at least one bit of the motion vector predictor index of a current block depends on another parameter or syntax element of said current block that is an indicator of a complexity of motion in the current block.

According to a sixteenth aspect of the present invention there is provided a method of decoding a motion vector predictor index, comprising: generating a list of motion vector predictor candidates; decoding the motion vector predictor index using CABAC decoding, wherein a context variable for at least one bit of the motion vector predictor index of a current block depends on a Skip flag of said current block; and using the decoded motion vector predictor index to identify one of the motion vector predictor candidates in the list.

According to a seventeenth aspect of the present invention there is provided a method of decoding a motion vector predictor index, comprising: generating a list of motion vector predictor candidates; decoding the motion vector predictor index using CABAC decoding, wherein a context variable for at least one bit of the motion vector predictor index of a current block depends on another parameter or syntax element of said current block that is available prior to decoding of the motion vector predictor index; and using the decoded motion vector predictor index to identify one of the motion vector predictor candidates in the list.

According to an eighteenth aspect of the present invention there is provided a method of decoding a motion vector predictor index, comprising: generating a list of motion vector predictor candidates; decoding the motion vector predictor index using CABAC decoding, wherein a context variable for at least one bit of the motion vector predictor index of a current block depends on another parameter or syntax element of said current block that is an indicator of a complexity of motion in the current block; and using the decoded motion vector predictor index to identify one of the motion vector predictor candidates in the list.

According to a nineteenth aspect of the present invention there is provided a device for encoding a motion vector predictor index, comprising: means for generating a list of motion vector predictor candidates; means for selecting one of the motion vector predictor candidates in the list; and means for generating a motion vector predictor index for the selected motion vector predictor candidate using CABAC coding, wherein a context variable for at least one bit of the motion vector predictor index of a current block depends on a Skip flag of said current block.

According to a twentieth aspect of the present invention there is provided a device for encoding a motion vector predictor index, comprising: means for generating a list of motion vector predictor candidates; means for selecting one of the motion vector predictor candidates in the list; and means for generating a motion vector predictor index for the selected motion vector predictor candidate using CABAC coding, wherein a context variable for at least one bit of the motion vector predictor index of a current block depends on another parameter or syntax element of said current block that is available prior to decoding of the motion vector predictor index.

According to a twenty-first aspect of the present invention there is provided a device for encoding a motion vector predictor index, comprising: means for generating a list of motion vector predictor candidates; means for selecting one of the motion vector predictor candidates in the list; and means for generating a motion vector predictor index for the selected motion vector predictor candidate using CABAC coding, wherein a context variable for at least one bit of the motion vector predictor index of a current block depends on another parameter or syntax element of said current block that is an indicator of a complexity of motion in the current block.

According to a twenty-second aspect of the present invention there is provided a device for decoding a motion vector predictor index, comprising: means for generating a list of motion vector predictor candidates; means for decoding the motion vector predictor index using CABAC decoding, wherein a context variable for at least one bit of the motion vector predictor index of a current block depends on a Skip flag of said current block; and means for using the decoded motion vector predictor index to identify one of the motion vector predictor candidates in the list.

According to a twenty-third aspect of the present invention there is provided a device for decoding a motion vector predictor index, comprising: means for generating a list of motion vector predictor candidates; means for decoding the motion vector predictor index using CABAC decoding, wherein a context variable for at least one bit of the motion vector predictor index of a current block depends on another parameter or syntax element of said current block that is available prior to decoding of the motion vector predictor index; and means for using the decoded motion vector predictor index to identify one of the motion vector predictor candidates in the list.

According to a twenty-fourth aspect of the present invention there is provided a device for decoding a motion vector predictor index, comprising: means for generating a list of motion vector predictor candidates; means for decoding the motion vector predictor index using CABAC decoding, wherein a context variable for at least one bit of the motion vector predictor index of a current block depends on another parameter or syntax element of said current block that is an indicator of a complexity of motion in the current block; and means for using the decoded motion vector predictor index to identify one of the motion vector predictor candidates in the list.

According to a twenty-fifth aspect of the present invention there is provided a method of encoding information about a motion information predictor, comprising: selecting one of a plurality of motion information predictor candidates; and encoding information for identifying the selected motion information predictor candidate using CABAC coding, wherein the CABAC coding comprises, for at least one bit of said information, using the same context variable used for another inter prediction mode when one or both of a Triangle Merge mode or a Merge with Motion Vector Difference (MMVD) Merge mode is used.

According to a twenty-sixth aspect of the present invention there is provided a method of decoding information about a motion information predictor, comprising: decoding information for identifying one of a plurality of motion information predictor candidates using CABAC decoding; and using the decoded information to select the one of the plurality of motion information predictor candidates, wherein the CABAC decoding comprises, for at least one bit of said information, using the same context variable used for another inter prediction mode when one or both of a Triangle Merge mode or a Merge with Motion Vector Difference (MMVD) Merge mode is used.

For the twenty-fifth aspect or twenty-sixth aspect of the present invention, following features may be provided according to an embodiment thereof.

Suitably, all bits except for a first bit of the information are bypass CABAC coded or bypass CABAC decoded. Suitably, the first bit is CABAC coded or CABAC decoded. Suitably, the another inter prediction mode comprises one or both of a Merge mode or an Affine Merge mode. Suitably, the another inter prediction mode comprises a Multi-Hypothesis Intra Inter (MHII) Merge mode. Suitably, the plurality of motion information predictor candidates for the another inter prediction mode comprises an ATMVP candidate. Suitably, the CABAC coding or CABAC decoding comprises using the same context variable for both when the Triangle Merge mode is used and the MMVD Merge mode is used. Suitably, at least one bit of said information is CABAC coded or CABAC decoded when a Skip mode is used. Suitably, the Skip mode comprises one or more of a Merge Skip mode, an Affine Merge Skip mode, a Triangle Merge Skip mode, or a Merge with Motion Vector Difference (MMVD) Merge Skip mode.

According to a twenty-seventh aspect of the present invention there is provided a method of encoding information about a motion information predictor, comprising: selecting one of a plurality of motion information predictor candidates; and encoding information for identifying the selected motion information predictor candidate, wherein encoding the information comprises bypass CABAC coding at least one bit of said information when one or both of a Triangle Merge mode or a Merge with Motion Vector Difference (MMVD) Merge mode is used.

According to a twenty-eighth aspect of the present invention there is provided a method of decoding information about a motion information predictor, comprising: decoding information for identifying one of a plurality of motion information predictor candidates; and using the decoded information to select the one of the plurality of motion information predictor candidates, wherein decoding the information comprises bypass CABAC decoding at least one bit of said information when one or both of a Triangle Merge mode or a Merge with Motion Vector Difference (MMVD) Merge mode is used.

For the twenty-seventh aspect or twenty-eighth aspect of the present invention, following features may be provided according to an embodiment thereof.

Suitably, all bits except for a first bit of the information are bypass CABAC coded or bypass CABAC decoded. Suitably, the first bit is CABAC coded or CABAC decoded. Suitably, all bits of said information are bypass CABAC coded or bypass CABAC decoded when one or both of the Triangle Merge mode or the MMVD Merge mode is used. Suitably, all bits of said information are bypass CABAC coded or bypass CABAC decoded.

Suitably, at least one bit of said information is CABAC coded or CABAC decoded when an Affine Merge mode is used. Suitably, all bits of said information are bypass CABAC coded or bypass CABAC decoded except when the Affine Merge mode is used.

Suitably, at least one bit of said information is CABAC coded or CABAC decoded when one or both of a Merge mode or a Multi-Hypothesis Intra Inter (MHII) Merge mode is used. Suitably, all bits of said information are bypass CABAC coded or bypass CABAC decoded except when one or both of the Merge mode or the Multi-Hypothesis Intra Inter (MHII) Merge mode is used.

Suitably, at least one bit of said information is CABAC coded or CABAC decoded when the plurality of motion information predictor candidates comprises an ATMVP candidate. Suitably, all bits of said information are bypass CABAC coded or bypass CABAC decoded except when the plurality of motion information predictor candidates comprises an ATMVP candidate.

Suitably, at least one bit of said information is CABAC coded or CABAC decoded when a Skip mode is used. Suitably, all bits of said information are bypass CABAC coded or bypass CABAC decoded except when the Skip mode is used. Suitably, the Skip mode comprises one or more of a Merge Skip mode, an Affine Merge Skip mode, a Triangle Merge Skip mode, or a Merge with Motion Vector Difference (MMVD) Merge Skip mode.

For the twenty-fifth aspect, twenty-sixth aspect, twenty-seventh aspect, or twenty-eighth aspect of the present invention, following features may be provided according to an embodiment thereof.

Suitably, the at least one bit comprises a first bit of said information. Suitably, said information comprises a motion information predictor index or a flag. Suitably, a motion information predictor candidate comprises information for obtaining a motion vector.

For the twenty-fifth aspect or twenty-seventh aspect of the present invention, following features may be provided according to an embodiment thereof.

Suitably, the method further comprises including, in a bitstream, information for indicating use of one of the Triangle Merge mode, the MMVD Merge mode, a Merge mode, an Affine Merge mode, or a Multi-Hypothesis Intra Inter (MHII) Merge mode. Suitably, the method further comprises including, in a bitstream, information for determining a maximum number of motion information predictor candidates includable in the plurality of motion information predictor candidates.

For the twenty-sixth aspect or twenty-eighth aspect of the present invention, following features may be provided according to an embodiment thereof.

Suitably, the method further comprises obtaining, from a bitstream, information for indicating use of one of the Triangle Merge mode, the MMVD Merge mode, a Merge mode, an Affine Merge mode, or a Multi-Hypothesis Intra Inter (MHII) Merge mode. Suitably, the method further comprises obtaining, from a bitstream, information for determining a maximum number of motion information predictor candidates includable in the plurality of motion information predictor candidates.

According to a twenty-ninth aspect of the present invention there is provided a device for encoding information about a motion information predictor, comprising: means for selecting one of a plurality of motion information predictor candidates; and means for encoding information for identifying the selected motion information predictor candidate using CABAC coding, wherein the CABAC coding comprises, for at least one bit of said information, using the same context variable used for another inter prediction mode when one or both of a Triangle Merge mode or a Merge with Motion Vector Difference (MMVD) Merge mode is used. Suitably, the device comprises means for performing a method of encoding information about a motion information predictor according to the twenty-fifth aspect or twenty-seventh aspect of the present invention.

According to a thirtieth aspect of the present invention there is provided a device for encoding information about a motion information predictor, comprising: means for selecting one of a plurality of motion information predictor candidates; and means for encoding information for identifying the selected motion information predictor candidate, wherein encoding the information comprises bypass CABAC coding at least one bit of said information when one or both of a Triangle Merge mode or a Merge with Motion Vector Difference (MMVD) Merge mode is used. Suitably, the device comprises means for performing a method of encoding information about a motion information predictor according to the twenty-fifth aspect or twenty-seventh aspect of the present invention.

According to a thirty-first aspect of the present invention there is provided a device for decoding information about a motion information predictor, comprising: means for decoding information for identifying one of a plurality of motion information predictor candidates using CABAC decoding; and means for using the decoded information to select the one of the plurality of motion information predictor candidates, wherein the CABAC decoding comprises, for at least one bit of said information, using the same context variable used for another inter prediction mode when one or both of a Triangle Merge mode or a Merge with Motion Vector Difference (MMVD) Merge mode is used. Suitably, the device comprises means for performing a method of decoding information about a motion information predictor according to the twenty-sixth aspect or twenty-eighth aspect of the present invention.

According to a thirty-second aspect of the present invention there is provided a device for decoding information about a motion information predictor, comprising: means for decoding information for identifying one of a plurality of motion information predictor candidates; and means for using the decoded information to select the one of the plurality of motion information predictor candidates, wherein decoding the information comprises bypass CABAC decoding at least one bit of said information when one or both of a Triangle Merge mode or a Merge with Motion Vector Difference (MMVD) Merge mode is used. Suitably, the device comprises means for performing a method of decoding information about a motion information predictor according to the twenty-sixth aspect or twenty-eighth aspect of the present invention.

According to a thirty-third aspect of the present invention there is provided a method of encoding a motion vector predictor index, comprising: generating a list of motion vector predictor candidates; selecting one of the motion vector predictor candidates in the list; and generating a motion vector predictor index for the selected motion vector predictor candidate using CABAC coding, wherein a context variable for at least one bit of the motion vector predictor index of a current block is derived from a context variable of at least one of a Skip flag and an affine flag of the current block.

According to a thirty-fourth aspect of the present invention there is provided a method of decoding a motion vector predictor index, comprising: generating a list of motion vector predictor candidates; decoding the motion vector predictor index using CABAC decoding, wherein a context variable for at least one bit of the motion vector predictor index of a current block is derived from a context variable of at least one of a Skip flag and an affine flag of the current block; and using the decoded motion vector predictor index to identify one of the motion vector predictor candidates in the list.

According to a thirty-fifth aspect of the present invention there is provided a device for encoding a motion vector predictor index, comprising: means for generating a list of motion vector predictor candidates; means for selecting one of the motion vector predictor candidates in the list; and means for generating a motion vector predictor index for the selected motion vector predictor candidate using CABAC coding, wherein a context variable for at least one bit of the motion vector predictor index of a current block is derived from a context variable of at least one of a Skip flag and an affine flag of the current block.

According to a thirty-sixth aspect of the present invention there is provided a device for decoding a motion vector predictor index, comprising: means for generating a list of motion vector predictor candidates; means for decoding the motion vector predictor index using CABAC decoding, wherein a context variable for at least one bit of the motion vector predictor index of a current block is derived from a context variable of at least one of a Skip flag and an affine flag of the current block; and means for using the decoded motion vector predictor index to identify one of the motion vector predictor candidates in the list.

According to a thirty-seventh aspect of the present invention there is provided a method of encoding a motion vector predictor index, comprising: generating a list of motion vector predictor candidates; selecting one of the motion vector predictor candidates in the list; and generating a motion vector predictor index for the selected motion vector predictor candidate using CABAC coding, wherein a context variable for at least one bit of the motion vector predictor index of a current block has only two different possible values.

According to a thirty-eighth aspect of the present invention there is provided a method of decoding a motion vector predictor index, comprising: generating a list of motion vector predictor candidates; decoding the motion vector predictor index using CABAC decoding, wherein a context variable for at least one bit of the motion vector predictor index of a current block has only two different possible values; and using the decoded motion vector predictor index to identify one of the motion vector predictor candidates in the list.

According to a thirty-ninth aspect of the present invention there is provided a device for encoding a motion vector predictor index, comprising: means for generating a list of motion vector predictor candidates; means for selecting one of the motion vector predictor candidates in the list; and means for generating a motion vector predictor index for the selected motion vector predictor candidate using CABAC coding, wherein a context variable for at least one bit of the motion vector predictor index of a current block has only two different possible values.

According to a fortieth aspect of the present invention there is provided a device for decoding a motion vector predictor index, comprising: means for generating a list of motion vector predictor candidates; means for decoding the motion vector predictor index using CABAC decoding, wherein a context variable for at least one bit of the motion vector predictor index of a current block has only two different possible values; and means for using the decoded motion vector predictor index to identify one of the motion vector predictor candidates in the list.

According to a forty-first aspect of the present invention there is provided a method of encoding a motion information predictor index, comprising: generating a list of motion information predictor candidates; when an Affine Merge mode is used, selecting one of the motion information predictor candidates in the list as an Affine Merge mode predictor; when a non-Affine Merge mode is used, selecting one of the motion information predictor candidates in the list as a non-Affine Merge mode predictor; and generating a motion information predictor index for the selected motion information predictor candidate using CABAC coding, one or more bits of the motion information predictor index being bypass CABAC coded. Suitably, the CABAC coding comprises using the same context variable for at least one bit of the motion information predictor index of a current block when the Affine Merge mode is used and when the non-Affine Merge mode is used. Alternatively, the CABAC coding comprises, for at least one bit of the motion information predictor index of a current block, using a first context variable when the Affine Merge mode is used or using a second context variable when the non-Affine Merge mode is used; and the method further comprises including data for indicating use of the Affine Merge mode in a bitstream when the Affine Merge mode is used. Suitably, the method further comprises including data for determining a maximum number of motion information predictor candidates includable in the generated list of motion information predictor candidates in a bitstream. Suitably, all bits except for a first bit of the motion information predictor index are bypass CABAC coded. Suitably, the first bit is CABAC coded. Suitably, the motion information predictor index for the selected motion information predictor candidate is encoded using the same syntax element when the Affine Merge mode is used and when the non-Affine Merge mode is used.

According to a forty-second aspect of the present invention there is provided a method of decoding a motion information predictor index, comprising: generating a list of motion information predictor candidates; decoding the motion information predictor index using CABAC decoding, one or more bits of the motion information predictor index being bypass CABAC decoded; when an Affine Merge mode is used, using the decoded motion information predictor index to identify one of the motion information predictor candidates in the list as an Affine Merge mode predictor; and when a non-Affine Merge mode is used, using the decoded motion information predictor index to identify one of the motion information predictor candidates in the list as a non-Affine Merge mode predictor. Suitably, the CABAC decoding comprises using the same context variable for at least one bit of the motion information predictor index of a current block when the Affine Merge mode is used and when the non-Affine Merge mode is used. Alternatively, the method further comprises obtaining, from a bitstream, data for indicating use of the Affine Merge mode, and the CABAC decoding comprises, for at least one bit of the motion information predictor index of a current block: when the obtained data indicates use of the Affine Merge mode, using a first context variable; and when the obtained data indicate use of the non-Affine Merge mode, using a second context variable. Suitably, the method further comprises obtaining, from a bitstream, data for indicating use of the Affine Merge mode, wherein the generated list of motion information predictor candidates comprises: when the obtained data indicates use of the Affine Merge mode, Affine Merge mode predictor candidates; and when the obtained data indicate use of the non-Affine Merge mode, non-Affine Merge mode predictor candidates. Suitably, the method further comprises obtaining, from a bitstream, data for determining a maximum number of motion information predictor candidates includable in the generated list of motion information predictor candidates. Suitably, all bits except for a first bit of the motion information predictor index are bypass CABAC decoded. Suitably, the first bit is CABAC decoded. Suitably, decoding the motion information predictor index comprises parsing, from a bitstream, the same syntax element when the Affine Merge mode is used and when the non-Affine Merge mode is used. Suitably, a motion information predictor candidate comprises information for obtaining a motion vector. Suitably, the generated list of motion information predictor candidates includes an ATMVP candidate. Suitably, the generated list of motion information predictor candidates has the same maximum number of motion information predictor candidates includable therein when the Affine Merge mode is used and when the non-Affine Merge mode is used.

According to a forty-third aspect of the present invention there is provided a device for encoding a motion information predictor index, comprising: means for generating a list of motion information predictor candidates; means for selecting, when an Affine Merge mode is used, one of the motion information predictor candidates in the list as an Affine Merge mode predictor; means for selecting, when a non-Affine Merge mode is used, one of the motion information predictor candidates in the list as a non-Affine Merge mode predictor; and means for generating a motion information predictor index for the selected motion information predictor candidate using CABAC coding, one or more bits of the motion information predictor index being bypass CABAC coded. Suitably, the device comprises means for performing a method of encoding a motion information predictor index according to the forty-first aspect.

According to a forty-fourth aspect of the present invention there is provided a device for decoding a motion information predictor index, comprising: means for generating a list of motion information predictor candidates; means for decoding the motion information predictor index using CABAC decoding, one or more bits of the motion information predictor index being bypass CABAC decoded; means for, when an Affine Merge mode is used, using the decoded motion information predictor index to identify one of the motion information predictor candidates in the list as an Affine Merge mode predictor; and means for, when a non-Affine Merge mode is used, using the decoded motion information predictor index to identify one of the motion information predictor candidates in the list as a non-Affine Merge mode predictor. Suitably, the device comprises means for performing a method of decoding a motion information predictor index according to the forty-second aspect.

According to a forty-fifth aspect of the present invention there is provided a method of encoding a motion information predictor index for an Affine Merge mode, comprising: generating a list of motion information predictor candidates; selecting one of the motion information predictor candidates in the list as an Affine Merge mode predictor; and generating a motion information predictor index for the selected motion information predictor candidate using CABAC coding, one or more bits of the motion information predictor index being bypass CABAC coded. Suitably, when a non-Affine Merge mode is used, the method further comprises selecting one of the motion information predictor candidates in the list as a non-Affine Merge mode predictor. Suitably, the CABAC coding comprises, for at least one bit of the motion information predictor index of a current block, using a first context variable when the Affine Merge mode is used or using a second context variable when the non-Affine Merge mode is used; and the method further comprises including data for indicating use of the Affine Merge mode in a bitstream when the Affine Merge mode is used. Alternatively, the CABAC coding comprises using the same context variable for at least one bit of the motion information predictor index of a current block when the Affine Merge mode is used and when the non-Affine Merge mode is used. Suitably, the method further comprises including data for determining a maximum number of motion information predictor candidates includable in the generated list of motion information predictor candidates in a bitstream. Suitably, all bits except for a first bit of the motion information predictor index are bypass CABAC coded. Suitably, the first bit is CABAC coded. Suitably, the motion information predictor index for the selected motion information predictor candidate is encoded using the same syntax element when the Affine Merge mode is used and when the non-Affine Merge mode is used.

According to a forty-sixth aspect of the present invention there is provided a method of decoding a motion information predictor index for an Affine Merge mode, comprising: generating a list of motion information predictor candidates; decoding the motion information predictor index using CABAC decoding, one or more bits of the motion information predictor index being bypass CABAC decoded; and when the Affine Merge mode is used, using the decoded motion information predictor index to identify one of the motion information predictor candidates in the list as an Affine Merge mode predictor. Suitably, when a non-Affine Merge mode is used, the method further comprises using the decoded motion information predictor index to identify one of the motion information predictor candidates in the list as a non-Affine Merge mode predictor. Suitably, the method further comprises: obtaining, from a bitstream, data for indicating use of the Affine Merge mode, and the CABAC decoding comprises, for at least one bit of the motion information predictor index of a current block: when the obtained data indicates use of the Affine Merge mode, using a first context variable; and when the obtained data indicates use of the non-Affine Merge mode, using a second context variable. Alternatively, the CABAC decoding comprises using the same context variable for at least one bit of the motion information predictor index of a current block when the Affine Merge mode is used and when the non-Affine Merge mode is used. Suitably, the method further comprises obtaining, from a bitstream, data for indicating use of the Affine Merge mode, wherein the generated list of motion information predictor candidates comprises: when the obtained data indicates use of the Affine Merge mode, Affine Merge mode predictor candidates; and when the obtained data indicate use of the non-Affine Merge mode, non-Affine Merge mode predictor candidates. Suitably, decoding the motion information predictor index comprises parsing, from a bitstream, the same syntax element when the Affine Merge mode is used and when the non-Affine Merge mode is used. Suitably, the method further comprises obtaining, from a bitstream, data for determining a maximum number of motion information predictor candidates includable in the generated list of motion information predictor candidates. Suitably, all bits except for a first bit of the motion information predictor index are bypass CABAC decoded. Suitably, the first bit is CABAC decoded. Suitably, a motion information predictor candidate comprises information for obtaining a motion vector. Suitably, the generated list of motion information predictor candidates includes an ATMVP candidate. Suitably, the generated list of motion information predictor candidates has the same maximum number of motion information predictor candidates includable therein when the Affine Merge mode is used and when a non-Affine Merge mode is used.

According to a forty-seventh aspect of the present invention there is provided a device for encoding a motion information predictor index for an Affine Merge mode, comprising: means for generating a list of motion information predictor candidates; means for selecting one of the motion information predictor candidates in the list as an Affine Merge mode predictor; and means for generating a motion information predictor index for the selected motion information predictor candidate using CABAC coding, one or more bits of the motion information predictor index being bypass CABAC coded. Suitably, the device comprises means for performing a method of encoding a motion information predictor index according to the forty-fifth aspect.

According to a forty-eighth aspect of the present invention there is provided a device for decoding a motion information predictor index for an Affine Merge mode, comprising: means for generating a list of motion information predictor candidates; means for decoding the motion information predictor index using CABAC decoding, one or more bits of the motion information predictor index being bypass CABAC decoded; and means for, when the Affine Merge mode is used, using the decoded motion information predictor index to identify one of the motion information predictor candidates in the list as an Affine Merge mode predictor. Suitably, the device comprises means for performing a method of decoding a motion information predictor index according to the forty-sixth aspect.

Yet further aspects of the present invention relate to programs which when executed by a computer or processor cause the computer or processor to carry out any of the methods of the aforementioned aspects. The program may be provided on its own or may be carried on, by or in a carrier medium. The carrier medium may be non-transitory, for example a storage medium, in particular a computer-readable storage medium. The carrier medium may also be transitory, for example a signal or other transmission medium. The signal may be transmitted via any suitable network, including the Internet.

Yet further aspects of the present in invention relate to a camera comprising a device according to any of the aforementioned device aspects. In one embodiment the camera further comprises zooming means. In one embodiment the camera is adapted to indicate when said zooming means is operational and signal an inter prediction mode in dependence on said indication that the zooming means is operational. In another embodiment the camera further comprises panning means. In another embodiment the camera is adapted to indicate when said panning means is operational and signal an inter prediction mode in dependence on said indication that the panning means is operational.

According to yet another aspect of the present invention there is provided a mobile device comprising a camera embodying any of the camera aspects above. In one embodiment the mobile device further comprises at least one positional sensor adapted to sense a change in orientation of the mobile device. In one embodiment the mobile device is adapted to signal an inter prediction mode in dependence on said sensing a change in orientation of the mobile device.

Further features of the invention are characterised by the other independent and dependent claims.

Any feature in one aspect of the invention may be applied to other aspects of the invention, in any appropriate combination. In particular, method aspects may be applied to apparatus aspects, and vice versa. Furthermore, features implemented in hardware may be implemented in software, and vice versa. Any reference to software and hardware features herein should be construed accordingly Any apparatus feature as described herein may also be provided as a method feature, and vice versa. As used herein, means plus function features may be expressed alternatively in terms of their corresponding structure, such as a suitably programmed processor and associated memory.

It should also be appreciated that particular combinations of the various features described and defined in any aspects of the invention can be implemented and/or supplied and/or used independently.

Reference will now be made, by way of example, to the accompanying drawings, in which:

FIG. 1 is a diagram for use in explaining a coding structure used in HEVC;

FIG. 2 is a block diagram schematically illustrating a data communication system in which one or more embodiments of the invention may be implemented;

FIG. 3 is a block diagram illustrating components of a processing device in which one or more embodiments of the invention may be implemented;

FIG. 4 is a flow chart illustrating steps of an encoding method according to embodiments of the invention;

FIG. 5 is a flow chart illustrating steps of a decoding method according to embodiments of the invention;

FIGS. 6a and 6b illustrate spatial and temporal blocks that can be used to generate motion vector predictors;

FIG. 7 shows simplified steps of the process of an AMVP predictor set derivation;

FIG. 8 is a schematic of a motion vector derivation process of the Merge mode;

FIG. 9 illustrates segmentation of a current block and temporal motion vector prediction;

FIG. 10(a) illustrates a coding of a Merge index for HEVC, or when ATMVP is not enabled at SPS level;

FIG. 10(b) illustrates a coding of a Merge index when ATMVP is enabled at SPS level;

FIG. 11(a) illustrates a simple affine motion field;

FIG. 11(b) illustrates a more complex affine motion field;

FIG. 12 is a flow chart of the partial decoding process of some syntax elements related to the coding mode;

FIG. 13 is a flow chart illustrating Merge candidates derivation;

FIG. 14 illustrates a coding of a Merge index according to a first embodiment of the invention;

FIG. 15 is a flow chart of the partial decoding process of some syntax elements related to the coding mode in a twelfth embodiment of the invention;

FIG. 16 is a flow chart illustrating generating a list of merge candidates in the twelfth embodiment of the invention;

FIG. 17 is a block diagram for use in explaining a CABAC encoder suitable for use in embodiments of the invention;

FIG. 18 is a schematic block diagram of a communication system for implementation of one or more embodiments of the invention;

FIG. 19 is a schematic block diagram of a computing device;

FIG. 20 is a diagram illustrating a network camera system;

FIG. 21 is a diagram illustrating a smart phone;

FIG. 22 is a flow chart of the partial decoding process of some syntax elements related to the coding mode according to a sixteenth embodiment;

FIG. 23 is a flow chart illustrating use of a single index signalling scheme for both a Merge mode and an Affine Merge mode according to an embodiment;

FIG. 24 is a flow chart illustrating Affine Merge candidate derivation process for the Affine Merge mode according to an embodiment;

FIG. 25(a) and FIG. 25(b) illustrate a predictor derivation process for a Triangle Merge mode according to an embodiment;

FIG. 26 is a flow chart of a decoding process for inter prediction modes for a current Coding Unit according to an embodiment;

FIG. 27(a) illustrates a coding of a flag for a Merge with Motion Vector Difference (MMVD) Merge mode according to an embodiment;

FIG. 27(b) illustrates a coding of an index for the Triangle Merge mode according to an embodiment;

FIG. 28 is a flow chart illustrating an Affine Merge candidate derivation process for the Affine Merge mode with an ATMVP candidate according to an embodiment;

FIG. 29 is a flow chart of a decoding process for inter prediction modes according to an eighteenth embodiment;

FIG. 30(a) illustrates a coding of a flag for a Merge with Motion Vector Difference (MMVD) Merge mode according to a nineteenth embodiment;

FIG. 30(b) illustrates a coding of an index for the Triangle Merge mode according to the nineteenth embodiment;

FIG. 30(c) illustrates a coding of an index for the Affine Merge mode or the Merge mode according to the nineteenth embodiment; and

FIG. 31 is a flow chart of a decoding process for inter prediction modes according to the nineteenth embodiment.

DETAILED DESCRIPTION

Embodiments of the present invention described below relate to improving encoding and decoding of indexes/flags/information/data using CABAC. It is understood that according to alternative embodiments of the present invention, an implementation for improving other context based arithmetic coding scheme functionally similar to the CABAC is also possible. Before describing the embodiments, video encoding and decoding techniques and related encoders and decoders will be described.

In this specification ‘signalling’ may refer to inserting into (providing/including/encoding in), or extracting/obtaining (decoding) from, a bitstream information about one or more syntax element representing use, disuse, enabling or disabling of a mode (e.g. an inter prediction mode) or other information (such as information about a selection).

FIG. 1 relates to a coding structure used in the High Efficiency Video Coding (HEVC) video standard. A video sequence 1 is made up of a succession of digital images i. Each such digital image is represented by one or more matrices. The matrix coefficients represent pixels.

An image 2 of the sequence may be divided into slices 3. A slice may in some instances constitute an entire image. These slices are divided into non-overlapping Coding Tree Units (CTUs). A Coding Tree Unit (CTU) is the basic processing unit of the High Efficiency Video Coding (HEVC) video standard and conceptually corresponds in structure to macroblock units that were used in several previous video standards. A CTU is also sometimes referred to as a Largest Coding Unit (LCU). A CTU has luma and chroma component parts, each of which component parts is called a Coding Tree Block (CTB). These different color components are not shown in FIG. 1.

A CTU is generally of size 64 pixels×64 pixels for HEVC, yet for VVC this size can be 128 pixels×128 pixels. Each CTU may in turn be iteratively divided into smaller variable-size Coding Units (CUs) 5 using a quadtree decomposition.

Coding units are the elementary coding elements and are constituted by two kinds of sub-unit called a Prediction Unit (PU) and a Transform Unit (TU). The maximum size of a PU or TU is equal to the CU size. A Prediction Unit corresponds to the partition of the CU for prediction of pixels values. Various different partitions of a CU into PUs are possible as shown by 6 including a partition into 4 square PUs and two different partitions into 2 rectangular PUs. A Transform Unit is an elementary unit that is subjected to spatial transformation using DCT. A CU can be partitioned into TUs based on a quadtree representation 7. So a slice, a tile, a CTU/LCU, a CTB, a CU, a PU, a TU, or a block of pixels/samples may be referred to as an image portion, i.e. a portion of the image 2 of the sequence.

Each slice is embedded in one Network Abstraction Layer (NAL) unit. In addition, the coding parameters of the video sequence are stored in dedicated NAL units called parameter sets. In HEVC and H.264/AVC two kinds of parameter sets NAL units are employed: first, a Sequence Parameter Set (SPS) NAL unit that gathers all parameters that are unchanged during the whole video sequence. Typically, it handles the coding profile, the size of the video frames and other parameters. Secondly, a Picture Parameter Set (PPS) NAL unit includes parameters that may change from one image (or frame) to another of a sequence. HEVC also includes a Video Parameter Set (VPS) NAL unit which contains parameters describing the overall structure of the bitstream. The VPS is a new type of parameter set defined in HEVC, and applies to all of the layers of a bitstream. A layer may contain multiple temporal sub-layers, and all version 1 bitstreams are restricted to a single layer. HEVC has certain layered extensions for scalability and multiview and these will enable multiple layers, with a backwards compatible version 1 base layer.

FIG. 2 and FIG. 18 illustrate data communication systems in which one or more embodiments of the invention may be implemented. The data communication system comprises a transmission device, e.g. a server 201 in FIG. 2 or a content provider 150 in FIG. 18, which is operable to transmit data packets of a data stream 204 (or bitstream 101 in FIG. 18) to a receiving device, e.g. a client terminal 202 in FIG. 2 or a content consumer 100 in FIG. 18, via a data communication network 200. The data communication network 200 may be a Wide Area Network (WAN) or a Local Area Network (LAN). Such a network may be for example a wireless network (Wifi/802.11a or b or g), an Ethernet network, an Internet network or a mixed network composed of several different networks. In a particular embodiment of the invention the data communication system may be a digital television broadcast system in which the server 201 (or a content provider 150 in FIG. 18) sends the same data content to multiple clients (or content consumers).

The data stream 204 (or bitstream 101) provided by the server 201 (or the content provider 150) may be composed of multimedia data representing video and audio data. Audio and video data streams may, in some embodiments of the invention, be captured by the server 201 (or the content provider 150) using a microphone and a camera respectively. In some embodiments data streams may be stored on the server 201 (or the content provider 150) or received by the server 201 (or the content provider 150) from another data provider, or generated at the server 201 (or the content provider 150). The server 201 (or the content provider 150) is provided with an encoder for encoding video and audio streams (e.g. original sequence of images 151 in FIG. 18) in particular to provide a compressed bitstream 204, 101 for transmission that is a more compact representation of the data presented as input to the encoder.

In order to obtain a better ratio of the quality of transmitted data to quantity of transmitted data, the compression of the video data may be for example in accordance with the HEVC format or H.264/AVC format or VVC format.

The client 202 (or the content consumer 100) receives the transmitted bitstream and decodes the reconstructed bitstream to reproduce video images (e.g. video signal 109 in FIG. 18) on a display device and the audio data by a loud speaker.

Although a streaming scenario is considered in the example of FIG. 2 or FIG. 18, it will be appreciated that in some embodiments of the invention the data communication between an encoder and a decoder may be performed using for example a media storage device such as an optical disc.

In one or more embodiments of the invention a video image may be transmitted with data representative of compensation offsets for application to reconstructed pixels of the image to provide filtered pixels in a final image.

FIG. 3 schematically illustrates a processing device 300 configured to implement at least one embodiment of the present invention. The processing device 300 may be a device such as a micro-computer, a workstation or a light portable device. The device 300 comprises a communication bus 313 connected to:

a central processing unit 311, such as a microprocessor, denoted CPU;

a read only memory 307, denoted ROM, for storing computer programs for implementing the invention;

a random access memory 312, denoted RAM, for storing the executable code of the method of embodiments of the invention as well as the registers adapted to record variables and parameters necessary for implementing the method of encoding a sequence of digital images and/or the method of decoding a bitstream according to embodiments of the invention; and

a communication interface 302 connected to a communication network 303 over which digital data to be processed are transmitted or received.

Optionally, the apparatus 300 may also include the following components:

a data storage means 304 such as a hard disk, for storing computer programs for implementing methods of one or more embodiments of the invention and data used or produced during the implementation of one or more embodiments of the invention;

a disk drive 305 for a disk 306, the disk drive being adapted to read data from the disk 306 or to write data onto said disk; and

a screen 309 for displaying data and/or serving as a graphical interface with the user, by means of a keyboard 310 or any other pointing/input means.

The apparatus 300 can be connected to various peripherals, such as for example a digital camera 320 or a microphone 308, each being connected to an input/output card (not shown) so as to supply multimedia data to the apparatus 300.

The communication bus provides communication and interoperability between the various elements included in the apparatus 300 or connected to it. The representation of the bus is not limiting and in particular the central processing unit is operable to communicate instructions to any element of the apparatus 300 directly or by means of another element of the apparatus 300.

The disk 306 can be replaced by any information medium such as for example a compact disk (CD-ROM), rewritable or not, a ZIP disk or a memory card and, in general terms, by an information storage means that can be read by a microcomputer or by a microprocessor, integrated or not into the apparatus, possibly removable and adapted to store one or more programs whose execution enables the method of encoding a sequence of digital images and/or the method of decoding a bitstream according to the invention to be implemented.

The executable code may be stored either in read only memory 307, on the hard disk 304 or on a removable digital medium such as for example a disk 306 as described previously. According to a variant, the executable code of the programs can be received by means of the communication network 303, via the interface 302, in order to be stored in one of the storage means of the apparatus 300 before being executed, such as the hard disk 304.

The central processing unit 311 is adapted to control and direct the execution of the instructions or portions of software code of the program or programs according to the invention, instructions that are stored in one of the aforementioned storage means. On powering up, the program or programs that are stored in a non-volatile memory, for example on the hard disk 304, the disk 306 or in the read only memory 307, are transferred into the random access memory 312, which then contains the executable code of the program or programs, as well as registers for storing the variables and parameters necessary for implementing the invention.

In this embodiment, the apparatus is a programmable apparatus which uses software to implement the invention. However, alternatively, the present invention may be implemented in hardware (for example, in the form of an Application Specific Integrated Circuit or ASIC).

FIG. 4 illustrates a block diagram of an encoder according to at least one embodiment of the invention. The encoder is represented by connected modules, each module being adapted to implement, for example in the form of programming instructions to be executed by the CPU 311 of device 300, at least one corresponding step of a method implementing at least one embodiment of encoding an image of a sequence of images according to one or more embodiments of the invention.

An original sequence of digital images i0 to in 401 is received as an input by the encoder 400. Each digital image is represented by a set of samples, sometimes also referred to as pixels (hereinafter, they are referred to as pixels).

A bitstream 410 is output by the encoder 400 after implementation of the encoding process. The bitstream 410 comprises a plurality of encoding units or slices, each slice comprising a slice header for transmitting encoding values of encoding parameters used to encode the slice and a slice body, comprising encoded video data.

The input digital images i0 to in 401 are divided into blocks of pixels by module 402. The blocks correspond to image portions and may be of variable sizes (e.g. 4×4, 8×8, 16×16, 32×32, 64×64, 128×128 pixels and several rectangular block sizes can be also considered). A coding mode is selected for each input block. Two families of coding modes are provided: coding modes based on spatial prediction coding (Intra prediction), and coding modes based on temporal prediction (Inter coding, Merge, SKIP). The possible coding modes are tested.

Module 403 implements an Intra prediction process, in which the given block to be encoded is predicted by a predictor computed from pixels of the neighborhood of said block to be encoded. An indication of the selected Intra predictor and the difference between the given block and its predictor is encoded to provide a residual if the Intra coding is selected.

Temporal prediction is implemented by motion estimation module 404 and motion compensation module 405. Firstly a reference image from among a set of reference images 416 is selected, and a portion of the reference image, also called reference area or image portion, which is the closest area (closest in terms of pixel value similarity) to the given block to be encoded, is selected by the motion estimation module 404. Motion compensation module 405 then predicts the block to be encoded using the selected area. The difference between the selected reference area and the given block, also called a residual block, is computed by the motion compensation module 405. The selected reference area is indicated using a motion vector.

Thus, in both cases (spatial and temporal prediction), a residual is computed by subtracting the predictor from the original block when it is not in the SKIP mode.

In the INTRA prediction implemented by module 403, a prediction direction is encoded. In the Inter prediction implemented by modules 404, 405, 416, 418, 417, at least one motion vector or data for identifying such motion vector is encoded for the temporal prediction. Information relevant to the motion vector and the residual block is encoded if the Inter prediction is selected. To further reduce the bitrate, assuming that motion is homogeneous, the motion vector is encoded by difference with respect to a motion vector predictor. Motion vector predictors from a set of motion information predictor candidates is obtained from the motion vectors field 418 by a motion vector prediction and coding module 417.

The encoder 400 further comprises a selection module 406 for selection of the coding mode by applying an encoding cost criterion, such as a rate-distortion criterion. In order to further reduce redundancies a transform (such as DCT) is applied by transform module 407 to the residual block, the transformed data obtained is then quantized by quantization module 408 and entropy encoded by entropy encoding module 409. Finally, the encoded residual block of the current block being encoded is inserted into the bitstream 410 when it is not in the SKIP mode and the mode requires a residual block to be encoded in the bitstream.

The encoder 400 also performs decoding of the encoded image in order to produce a reference image (e.g. those in Reference images/pictures 416) for the motion estimation of the subsequent images. This enables the encoder and the decoder receiving the bitstream to have the same reference frames (reconstructed images or image portions are used). The inverse quantization (“dequantization”) module 411 performs inverse quantization (“dequantization”) of the quantized data, followed by an inverse transform by inverse transform module 412. The intra prediction module 413 uses the prediction information to determine which predictor to use for a given block and the motion compensation module 414 actually adds the residual obtained by module 412 to the reference area obtained from the set of reference images 416.

Post filtering is then applied by module 415 to filter the reconstructed frame (image or image portions) of pixels. In the embodiments of the invention an SAO loop filter is used in which compensation offsets are added to the pixel values of the reconstructed pixels of the reconstructed image. It is understood that post filtering does not always have to be performed. Also, any other type of post filtering may also be performed in addition to, or instead of, the SAO loop filtering.

FIG. 5 illustrates a block diagram of a decoder 60 which may be used to receive data from an encoder according an embodiment of the invention. The decoder is represented by connected modules, each module being adapted to implement, for example in the form of programming instructions to be executed by the CPU 311 of device 300, a corresponding step of a method implemented by the decoder 60.

The decoder 60 receives a bitstream 61 comprising encoded units (e.g. data corresponding to an image portion, a block or a coding unit), each one being composed of a header containing information on encoding parameters and a body containing the encoded video data. As explained with respect to FIG. 4, the encoded video data is entropy encoded, and the motion vector predictors' indexes are encoded, for a given image portion (e.g. a block or a CU), on a predetermined number of bits. The received encoded video data is entropy decoded by module 62. The residual data are then dequantized by module 63 and then an inverse transform is applied by module 64 to obtain pixel values.

The mode data indicating the coding mode are also entropy decoded and based on the mode, an INTRA type decoding or an INTER type decoding is performed on the encoded blocks (units/sets/groups) of image data.

In the case of INTRA mode, an INTRA predictor is determined by intra prediction module 65 based on the intra prediction mode specified in the bitstream.

If the mode is INTER, the motion prediction information is extracted from the bitstream so as to find (identify) the reference area used by the encoder. The motion prediction information comprises the reference frame index and the motion vector residual. The motion vector predictor is added to the motion vector residual by motion vector decoding module 70 in order to obtain the motion vector.

Motion vector decoding module 70 applies motion vector decoding for each image portion (e.g. current block or CU) encoded by motion prediction. Once an index of the motion vector predictor for the current block has been obtained, the actual value of the motion vector associated with the image portion (e.g. current block or CU) can be decoded and used to apply motion compensation by module 66. The reference image portion indicated by the decoded motion vector is extracted from a reference image 68 to apply the motion compensation 66. The motion vector(s) field data 71 is updated with the decoded motion vector in order to be used for the prediction of subsequent decoded motion vectors.

Finally, a decoded block is obtained. Where appropriate, post filtering is applied by post filtering module 67. A decoded video signal 69 is finally obtained and provided by the decoder 60.

CABAC

HEVC uses several types of entropy coding like the Context based Adaptive Binary Arithmetic Coding (CABAC), Golomb-rice Code, or simple binary representation called Fixed Length Coding. Most of the time, a binary encoding process is performed to represent different syntax elements. This binary encoding process is also very specific and depends on the different syntax elements. An arithmetic coding represents the syntax element according to their current probabilities. CABAC is an extension of the arithmetic coding which separates the probabilities of a syntax element depending on a ‘context’ defined by a context variable. This corresponds to a conditional probability. The context variable may be derived from the value of the current syntax for the top left block (A2 in FIG. 6b as described in more detail below) and the above left block (B3 in FIG. 6b ), which are already decoded.

CABAC has been adopted as a normative part of the H.264/AVC and H.265/HEVC standards. In H.264/AVC, it is one of two alternative methods of entropy coding. The other method specified in H.264/AVC is a low-complexity entropy-coding technique based on the usage of context-adaptively switched sets of variable-length codes, so-called Context-Adaptive Variable-Length Coding (CAVLC). Compared to CABAC, CAVLC offers reduced implementation costs at the price of lower compression efficiency. For TV signals in standard- or high-definition resolution, CABAC typically provides bit-rate savings of 10-20% relative to CAVLC at the same objective video quality. In HEVC, CABAC is one of the entropy coding method used. Many bits are also bypass CABAC coded (also expressed as CABAC bypass coded). Moreover, some syntax elements are coded with unary codes or Golomb codes which are other types of entropy codes.

FIG. 17 shows the main blocks of a CABAC encoder.

An input syntax element that is non-binary valued is binarized by a binarizer 1701. The coding strategy of CABAC is based on the finding that a very efficient coding of syntax-element values in a hybrid block-based video coder, like components of motion vector differences or transform-coefficient level values, can be achieved by employing a binarization scheme as a kind of preprocessing unit for the subsequent stages of context modeling and binary arithmetic coding. In general, a binarization scheme defines a unique mapping of syntax element values to sequences of binary decisions, so-called bins, which can be “bits” and hence also be interpreted in terms of a binary code tree. The design of binarization schemes in CABAC is based on a few elementary prototypes whose structure enables simple online calculation and which are adapted to some suitable model-probability distributions.

Each bin can be processed in one of two basic ways according to the setting of a switch 1702. When the switch is in the “regular” setting, the bin is supplied to a context modeler 1703 and a regular coding engine 1704. When the switch is in the “bypass” setting, the context modeler is bypassed and the bin is supplied to a bypass coding engine 1705. Another switch 1706 has “regular” and “bypass” settings similar to the switch 1702 so that the bins coded by the applicable one of the coding engines 1704 and 1705 can form a bitstream as the output of the CABAC encoder.

It is understood that the other switch 1706 may be used with a storage to group some of the bins (e.g. the bins for encoding an image portion such as a block or a coding unit) coded by the coding engine 1705 to provide a block of bypass coded data in the bitstream, and to group some of the bins (e.g. the bins for encoding a block or a coding unit) coded by the coding engine 1704 to provide another block of “regular” (or arithmetically) coded data in the bitstream. This separate grouping of bypass coded and regular coded data can lead to improved throughput during the decoding process (from being able to process the bypass coded data first/in parallel with the regular CABAC coded data).

By decomposing each syntax element value into a sequence of bins, further processing of each bin value in CABAC depends on the associated coding-mode decision, which can be either chosen as the regular or the bypass mode. The latter is chosen for bins related to the sign information or for lower significant bins, which are assumed to be uniformly distributed and for which, consequently, the whole regular binary arithmetic encoding process is simply bypassed. In the regular coding mode, each bin value is encoded by using the regular binary arithmetic-coding engine, where the associated probability model is either determined by a fixed choice, without any context modeling, or adaptively chosen depending on the related context model. As an important design decision, the latter case is generally applied to the most frequently observed bins only, whereas the other, usually less frequently observed bins, will be treated using a joint, typically zero-order probability model. In this way, CABAC enables selective context modeling on a sub-symbol level, and hence, provides an efficient instrument for exploiting inter-symbol redundancies at significantly reduced overall modeling or learning costs. For the specific choice of context models, four basic design types are employed in CABAC, where two of them are applied to coding of transform-coefficient levels only. The design of these four prototypes is based on a priori knowledge about the typical characteristics of the source data to be modeled and it reflects the aim to find a good compromise between the conflicting objectives of avoiding unnecessary modeling-cost overhead and exploiting the statistical dependencies to a large extent.

On the lowest level of processing in CABAC, each bin value enters the binary arithmetic encoder, either in regular or bypass coding mode. For the latter, a fast branch of the coding engine with a considerably reduced complexity is used while for the former coding mode, encoding of the given bin value depends on the actual state of the associated adaptive probability model that is passed along with the bin value to the M coder—a term that has been chosen for the table-based adaptive binary arithmetic coding engine in CABAC. A corresponding CABAC decoder then receives the bitstream output from the CABAC encoder, and processes the bypass coded data and the regular CABAC coded data accordingly. As the CABAC decoder processes the regular CABAC coded data, a context modeler (and its probability model) is updated so that the bins forming the bitstream can be decoded/processed (e.g. inverse binarized) correctly to obtain the syntax elements.

Inter Coding

HEVC uses 3 different INTER modes: the Inter mode (Advanced Motion Vector Prediction (AMVP) which signals motion information difference), the “classical” Merge mode (i.e. the “non-Affine Merge mode” or also known as “regular” Merge mode which does not signal motion information difference) and the “classical” Merge Skip mode (i.e. the “non-Affine Merge Skip” mode or also known as “regular” Merge Skip mode which does not signal motion information difference and also does not signal residual data for a sample value). The main difference between these modes is the data signalling in the bitstream. For the Motion vector coding, the current HEVC standard includes a competition based scheme for Motion vector prediction which was not present in earlier versions of the standard. It means that several candidates are competing with the rate distortion criterion at encoder side in order to find the best motion vector predictor or the best motion information for respectively the Inter coding mode (AMVP) or the Merge modes (i.e. the “classical/regular” Merge mode or the “classical/regular” Merge Skip mode). An index or a flag corresponding to the best predictor or the best candidate of the motion information is then inserted in the bitstream. The decoder can derive the same set of predictors or candidates and uses the best one according to the decoded index/flag. In the Screen Content Extension of HEVC, the new coding tool called Intra Block Copy (IBC) is signalled as any of those three INTER modes, the differentiation between IBC and the equivalent INTER mode being made by checking whether the reference frame is the current one. The IBC is also known as a Current Picture Referencing (CPR). This can be implemented e.g. by checking the reference index of the list L0, and deducing this is Intra Block Copy if this is the last frame in that list. Another way to do is comparing the Picture Order Count of current and reference frames: if they are equal, this is Intra Block Copy.

The design of the derivation of predictors and candidates is important in achieving the best coding efficiency without a disproportionate impact on complexity. In HEVC two motion vector derivations are used: one for Inter mode (Advanced Motion Vector Prediction (AMVP)) and one for Merge modes (Merge derivation process—for the classical Merge mode and the classical Merge Skip mode). The following describes these processes.

FIGS. 6a and 6b illustrates spatial and temporal blocks that can be used to generate motion vector predictors, e.g. in Advanced Motion Vector Prediction (AMVP) and Merge modes of HEVC coding and decoding systems, and FIG. 7 shows simplified steps of the process of the AMVP predictor set derivation.

Two spatial predictors, i.e. the two spatial motion vectors for the AMVP mode, are chosen among motion vectors of the top blocks (indicated by letter ‘B’) and the left blocks (indicated by letter ‘A’) including the top corner blocks (block B2) and left corner block (block A0), and one temporal predictor is chosen among motion vectors of the bottom right block (H) and centre block (Center) of the collocated block as represented in FIG. 6 a.

Table 1 below outlines the nomenclature used when referring to blocks in relative terms to the current block as shown in FIGS. 6a and 6b . This nomenclature is used as shorthand but it should be appreciated other systems of labelling may be used, in particular in future versions of a standard.

TABLE 1 Block label Relative positional description of neighbouring block A0 ‘Below left’ or ‘Left corner’-diagonally down and to the left of the current block A1 ‘Left’ or ‘Bottom left’-left of the bottom of the current block A2 ‘Top left’-left of the top of the current block B0 ‘Above right’-diagonally up and to the right of the current block B1 ‘Above’-above the top right of the current block B2 ‘Above left’ or ‘Top corner’-diagonally up and to the left of the current block B3 ‘Up’-above the top left of the current block H Bottom right of a collocated block in a reference frame Center A block within a collocated block in a reference frame

It should be noted that the ‘current block’ may be variable in size, for example 4×4, 16×16, 32×32, 64×64, 128×128 or any size in between. The dimensions of a block are preferably factors of 2 (i.e. 2{circumflex over ( )}n×2{circumflex over ( )}m where n and m are positive integers) as this results in a more efficient use of bits when using binary encoding. The current block need not be square, although this is often a preferable embodiment for coding complexity.

Turning to FIG. 7, a first step aims at selecting a first spatial predictor (Cand 1, 706) among the bottom left blocks A0 and A1, whose spatial positions are illustrated in FIG. 6a . To that end, these blocks are selected (700, 702) one after another in the given (i.e. predetermined/preset) order, and, for each selected block, following conditions are evaluated (704) in the given order, the first block for which conditions are fulfilled being set as a predictor:

the motion vector from the same reference list and the same reference image;

the motion vector from the other reference list and the same reference image;

the scaled motion vector from the same reference list and a different reference image; Or

the scaled motion vector from the other reference list and a different reference image.

If no value is found, the left predictor is considered as being unavailable. In this case, it indicates that the related blocks were INTRA coded or those blocks do not exist.

A following step aims at selecting a second spatial predictor (Cand 2, 716) among the above right block B0, above block B1, and left above (above left) block B2, whose spatial positions are illustrated in FIG. 6a . To that end, these blocks are selected (708, 710, 712) one after another in the given order, and, for each selected block, the above mentioned conditions are evaluated (714) in the given order, the first block for which the above mentioned conditions are fulfilled being set as a predictor.

Again, if no value is found, the top predictor is considered as being unavailable. In this case, it indicates that the related blocks were INTRA coded or those blocks do not exist.

In a next step (718), the two predictors, if both are available, are compared one to the other to remove one of them if they are equal (i.e. same motion vector values, same reference list, same reference index and the same direction type). If only one spatial predictor is available, the algorithm looks for a temporal predictor in a following step.

The temporal motion predictor (Cand 3, 726) is derived as follows: the bottom right (H, 720) position of the collocated block in a previous/reference frame is first considered in the availability check module 722. If it does not exist or if the motion vector predictor is not available, the centre of the collocated block (Centre, 724) is selected to be checked. These temporal positions (Centre and H) are depicted in FIG. 6a . In any case, scaling 723 is applied on those candidates to match the temporal distance between current frame and the first frame in the reference list.

The motion predictor value is then added to the set of predictors. Next, the number of predictors (Nb_Cand) is compared (728) to the maximum number of predictors (Max_Cand). As mentioned above, the maximum number of predictors (Max_Cand) of motion vector predictors that the derivation process of AMVP needs to generate is two in the current version of HEVC standard.

If this maximum number is reached, the final list or set of AMVP predictors (732) is built. Otherwise, a zero predictor is added (730) to the list. The zero predictor is a motion vector equal to (0, 0).

As illustrated in FIG. 7, the final list or set of AMVP predictors (732) is built from a subset of spatial motion predictor candidates (700 to 712) and from a subset of temporal motion predictor candidates (720, 724).

As mentioned above, a motion predictor candidate of the classical Merge mode or of the classical Merge Skip mode can represent all the required motion information: direction, list, reference frame index, and motion vectors (or any subset thereof for performing the prediction). An indexed list of several candidates is generated by the Merge derivation process. In the current HEVC design the maximum number of candidates for both Merge modes (i.e. the classical Merge mode and the classical Merge Skip mode) is equal to five (4 spatial candidates and 1 temporal candidate).

FIG. 8 is a schematic of a motion vector derivation process of the Merge modes (the classical Merge mode and the classical Merge Skip mode). In a first step of the derivation process, five block positions are considered (800 to 808). These positions are the spatial positions depicted in FIG. 6a with references A1, B1, B0, A0, and B2. In a following step, the availability of the spatial motion vectors is checked and at most five motion vectors are selected/obtained for consideration (810). A predictor is considered as available if it exists and if the block is not INTRA coded. Therefore, selecting the motion vectors corresponding to the five blocks as candidates is done according to the following conditions:

if the “left” A1 motion vector (800) is available (810), i.e. if it exists and if this block is not INTRA coded, the motion vector of the “left” block is selected and used as a first candidate in list of candidate (814);

if the “above” B1 motion vector (802) is available (810), the candidate “above” block motion vector is compared to “left” A1 motion vector (812), if it exists. If B1 motion vector is equal to A1 motion vector, B1 is not added to the list of spatial candidates (814). On the contrary, if B1 motion vector is not equal to A1 motion vector, B1 is added to the list of spatial candidates (814);

if the “above right” B0 motion vector (804) is available (810), the motion vector of the “above right” is compared to B1 motion vector (812). If B0 motion vector is equal to B1 motion vector, B0 motion vector is not added to the list of spatial candidates (814). On the contrary, if B0 motion vector is not equal to B1 motion vector, B0 motion vector is added to the list of spatial candidates (814);

if the “below left” A0 motion vector (806) is available (810), the motion vector of the “below left” is compared to A1 motion vector (812). If A0 motion vector is equal to A1 motion vector, A0 motion vector is not added to the list of spatial candidates (814). On the contrary, if A0 motion vector is not equal to A1 motion vector, A0 motion vector is added to the list of spatial candidates (814); and

if the list of spatial candidates doesn't contain four candidates, the availability of “above left” B2 motion vector (808) is checked (810). If it is available, it is compared to A1 motion vector and to B1 motion vector. If B2 motion vector is equal to A1 motion vector or to B1 motion vector, B2 motion vector is not added to the list of spatial candidates (814). On the contrary, if B2 motion vector is not equal to A1 motion vector or to B1 motion vector, B2 motion vector is added to the list of spatial candidates (814).

At the end of this stage, the list of spatial candidates comprises up to four candidates.

For the temporal candidate, two positions can be used: the bottom right position of the collocated block (816, denoted H in FIG. 6a ) and the centre of the collocated block (818). These positions are depicted in FIG. 6 a.

As described in relation to FIG. 7 for the temporal motion predictor of the AMVP motion vector derivation process, a first step aims at checking (820) the availability of the block at the H position. Next, if it is not available, the availability of the block at the centre position is checked (820). If at least one motion vector of these positions is available, the temporal motion vector can be scaled (822), if needed, to the reference frame having index 0, for both list L0 and L1, in order to create a temporal candidate (824) which is added to the list of Merge motion vector predictor candidates. It is positioned after the spatial candidates in the list. The lists L0 and L1 are 2 reference frame lists containing zero, one or more reference frames.

If the number (Nb_Cand) of candidates is strictly less (826) than the maximum number of candidates (Max_Cand information for determining that value is signalled in the bit-stream slice header and is equal to five in the current HEVC design) and if the current frame is of the B type, combined candidates are generated (828). Combined candidates are generated based on available candidates of the list of Merge motion vector predictor candidates. It mainly consists in combining (pairing) the motion information of one candidate of the list L0 with the motion information of one candidate of list L1.

If the number (Nb_Cand) of candidates remains strictly less (830) than the maximum number of candidates (Max_Cand), zero motion candidates are generated (832) until the number of candidates of the list of Merge motion vector predictor candidates reaches the maximum number of candidates.

At the end of this process, the list or set of Merge motion vector predictor candidates (i.e. a list or set of candidates for the Merge modes, which are the classical Merge mode and the classical Merge Skip mode) is built (834). As illustrated in FIG. 8, the list or set of Merge motion vector predictor candidates is built (834) from a subset of spatial candidates (800 to 808) and from a subset of temporal candidates (816, 818).

Alternative Temporal Motion Vector Prediction (ATMVP)

The alternative temporal motion vector prediction (ATMVP) is a special type of motion compensation. Instead of considering only one motion information for the current block from a temporal reference frame, each motion information of each collocated block is considered. So this temporal motion vector prediction gives a segmentation of the current block with the related motion information of each sub-block as depicted in FIG. 9.

In the VTM reference software, ATMVP is signalled as a Merge candidate inserted in the list of Merge candidates (i.e. a list or set of candidates for the Merge modes, which are the classical Merge mode and the classical Merge Skip mode). When ATMVP is enabled at SPS level, the maximum number of Merge candidates is increased by one. So 6 candidates are considered instead of 5, which would have been the case if this ATMVP mode is disabled. It is understood that according to an embodiment of the invention, the ATMVP may be signalled as an Affine Merge candidate (e.g. an ATMVP candidate) inserted in the list of Affine Merge candidates (i.e. a separate list or set of candidates for the Affine Merge modes, which are described in more detail below).

In addition when this prediction is enabled at SPS level, all bins of Merge index (i.e. an identifier or an index or information for identifying a candidate from the list of Merge candidates) are context coded by CABAC. While in HEVC, or when ATMVP is not enabled at SPS level in JEM, only the first bin is context coded and the remaining bins are context by-pass coded (i.e. bypass CABAC coded).

FIG. 10(a) illustrates the coding of the Merge index for HEVC, or when ATMVP is not enabled at SPS level in JEM. This corresponds to a unary max coding. In addition, in this FIG. 10(a) the first bit is CABAC coded and the other bits are bypass CABAC coded.

FIG. 10(b) illustrates the coding of the Merge index when ATMVP is enabled at SPS level. All bits are CABAC coded (from the 1^(st) to the 5^(th) bit). It should be noted that each bit for coding the index has its own context—in other words their probabilities used in the CABAC coding are separated.

Affine Mode

In HEVC, only translation motion model is applied for motion compensation prediction (MCP). While in the real world, there are many kinds of motion, e.g. zoom in/out, rotation, perspective motions and other irregular motions.

In the JEM, a simplified affine transform motion compensation prediction is applied and the general principle of Affine mode is described below based on an extract of document JVET-G1001 presented at a JVET meeting in Torino at 13-21 Jul. 2017. This entire document is hereby incorporated by reference insofar as it describes other algorithms used in JEM.

As shown in FIG. 11(a), the affine motion field of the block in this document is described by two control point motion vectors (it is understood that according to an embodiment of the invention, other affine models such as those with more control point motion vectors may also be used).

The motion vector field (MVF) of a block is described by the following equation:

$\begin{matrix} \left\{ \begin{matrix} {v_{x} = {{\frac{\left( {v_{1\; x} - v_{0\; x}} \right)}{w}x} - {\frac{\left( {v_{1\; y} - v_{0\; y}} \right)}{w}y} + v_{0x}}} \\ {v_{y} = {{\frac{\left( {v_{1\; y} - v_{0\; y}} \right)}{w}x} + {\frac{\left( {v_{1\; x} - v_{0\; x}} \right)}{w}y} + v_{0\; y}}} \end{matrix} \right. & (1) \end{matrix}$

Where (v_(0x), v_(0y)) is motion vector of the top-left corner control point, and (v_(1x), v_(1y)) is motion vector of the top-right corner control point. And w is the width of the block Cur (current block).

In order to further simplify the motion compensation prediction, sub-block based affine transform prediction is applied. The sub-block size M×N is derived as in Equation 2, where MvPre is the motion vector fraction accuracy ( 1/16 in JEM), (v_(2x), v_(2y)) is motion vector of the top-left control point, calculated according to Equation 1.

$\begin{matrix} \left\{ \begin{matrix} {M = {{clip}\; 3\ \left( {4,w,\frac{w \times MvPre}{\max\left( {{{abs}\;\left( {v_{1\; x} - v_{0\; x}} \right)},{{abs}\left( {v_{1y} - v_{0y}} \right)}} \right)}} \right)}} \\ {N = {{clip}\; 3\ \left( {4,h,\frac{h \times MvPre}{\max\left( {{{abs}\;\left( {v_{2\; x} - v_{0\; x}} \right)},{{abs}\left( {v_{2y} - v_{0y}} \right)}} \right)}} \right)}} \end{matrix} \right. & (2) \end{matrix}$

After derived by Equation 2, M and N may be adjusted downward if necessary to make it a divisor of w and h, respectively. h is the height of the current block Cur (current block).

To derive motion vector of each M×N sub-block, the motion vector of the center sample of each sub-block, as shown in FIG. 11(b), is calculated according to Equation 1, and rounded to 1/16 fraction accuracy. Then motion compensation interpolation filters are applied to generate the prediction of each sub-block with derived motion vector.

The affine mode is a motion compensation mode like the Inter modes (AMVP, “classical” Merge, or “classical” Merge Skip). Its principle is to generate one motion information per pixel according to 2 or 3 neighbouring motion information. In the JEM, the affine mode derives one motion information for each 4×4 block as depicted in FIG. 11(b) (each square is a 4×4 block, and the whole block in FIG. 11(b) is a 16×16 block which is divided into 16 blocks of such square of 4×4 size—each 4×4 square block having a motion vector associated therewith). It is understood that in embodiments of the present invention, the affine mode may drive one motion information for a block of a different size or shape as long as the one motion information can be derived.

According to an embodiment, this mode is made available for the AMVP mode and the Merge modes (i.e. the classical Merge mode which is also referred to as “non-Affine Merge mode” and the classical Merge Skip mode which is also referred to as “non-Affine Merge Skip mode”), by enabling the affine mode with a flag. This flag is CABAC coded. In an embodiment, the context depends on the sum of affine flags of the left block (position A2 of FIG. 6b ) and the above left block (position B3 of FIG. 6b ).

So three context variables (0, 1 or 2) are possible in the JEM for the affine flag given by the following formula:

Ctx=IsAffine(A2)+IsAffine(B3)

Where IsAffine(block) is a function which returns 0 if the block is not an affine block and 1 if the block is affine.

Affine Merge Candidate Derivation

In the JEM, the Affine Merge mode (or the Affine Merge Skip mode), also known as Subblock (Merge) mode, derives motion information for the current block from the first neighbouring block which is affine (i.e. the first neighbouring block that is coded using the affine mode) among blocks at positions A1, B1, B0, A0, B2. These positions are depicted in FIGS. 6a and 6b . However, how the affine parameter is derived is not completely defined, and the present invention aims to improve at least this aspect, for example by defining affine parameters of the Affine Merge mode so that it enables a wider selection choice for the Affine Merge candidates (i.e. not just the first neighbouring block which is affine but at least one other candidate is available for the selection with an identifier such as an index).

For example, according to some embodiments of the present invention, an Affine Merge mode with its own list of Affine Merge candidates (candidates for deriving/obtaining motion information for the Affine mode) and an Affine Merge index (for identifying one Affine Merge candidate from the list of Affine Merge candidates) is used to encode or decode a block.

Affine Merge Signalling

FIG. 12 is a flow chart of the partial decoding process of some syntax elements related to the coding mode for signalling use of the Affine Merge mode. In this figure the Skip flag (1201), the prediction mode (1211), the Merge flag (1203), the Merge Index (1208), and the affine flag (1206) can be decoded.

For all CU in an Inter slice, the Skip flag is decoded (1201). If the CU is not Skip (1202), the pred mode (Prediction mode) is decoded (1211). This syntax element indicates if the current CU is encoded in (is to be decoded in) an Inter or an Intra mode. Please note that if the CU is Skip (1202), its current mode is the Inter mode. If the CU is not skip (1202: No), the CU is coded in AMVP mode or in Merge mode. If the CU is Inter (1212), the Merge flag is decoded (1203). If the CU is Merge (1204) or if the CU is Skip (1202: Yes), it is verified/checked (1205) if the affine flag (1206) needs to be decoded, i.e. at (1205) a determination of whether the current CU could have been encoded in the affine mode is made. This flag is decoded if the current CU is a 2N×2N CU, which means in the current VVC that the height and the width of the CU shall be equal. Moreover, at least one neighbouring CU A1 or B1 or B0 or A0 or B2 must be coded with the affine mode (in either Affine Merge mode or an AMVP mode with the affine mode enabled). Eventually the current CU shall not be a 4×4 CU but by default the CU 4×4 are disabled in the VTM reference software. If this condition (1205) is false, it is sure that the current CU is coded with the classical Merge mode (or classical Merge Skip mode) as specified in HEVC, and a Merge Index is decoded (1208). If the Affine Flag (1206) is set equal to 1 (1207), the CU is a Merge affine CU (i.e. a CU encoded in the Affine Merge mode) or a Merge Skip Affine CU (i.e. a CU encoded in the Affine Merge Skip mode) and the Merge index (1208) doesn't need to be decoded (because the Affine Merge mode is used, i.e. the CU is to be decoded using the affine mode with the first neighbouring block that is affine). Otherwise, the current CU is a classical (basic) Merge or Merge Skip CU (i.e. a CU encoded in the classical Merge or Merge Skip mode) and the Merge candidate index (1208) is decoded.

Merge Candidates Derivation

FIG. 13 is a flow chart illustrating the Merge candidates (i.e. candidates for the classical Merge mode or the classical Merge Skip mode) derivation according to an embodiment. This derivation has been built on top of the motion vector derivation process of the Merge modes (i.e. a Merge candidate List derivation of HEVC) represented in FIG. 8. The main changes compared to HEVC are the addition of the ATMVP candidate (1319, 1321, 1323), the full duplicate checks of candidates (1325) and a new order of the candidates. The ATMVP prediction is set as a special candidate as it represents several motion information of the current CU. The value of the first sub-block (top left) is compared to the temporal candidate and the temporal candidate is not added to the list of Merge candidates if they are equal (1320). The ATMVP candidate is not compared to other spatial candidates. This is in contrast to the temporal candidate which is compared to each spatial candidate already in the list (1325) and not added to the Merge candidate list if it is a duplicate candidate.

When a spatial candidate is added in the list it is compared to the other spatial candidates in the list (1312) which is not the case in the final version of HEVC.

In the current VTM version the list of merge candidates is set in the following order as it has been determined to provide the best results over the coding test conditions:

-   A1 -   B1 -   B0 -   A0 -   ATMVP -   B2 -   TEMPORAL -   Combined -   Zero_MV

It is important to note that spatial candidate B2 is set after the ATMVP candidate.

In addition, when ATMVP is enabled at slice level the maximum number in the list of candidates is 6 instead of 5 of HEVC.

Other Inter Prediction Modes

In the first few embodiments described below (up to the sixteenth embodiment), the description thereof describes an encoding or decoding of an index for the (regular) MERGE mode and AFFINE MERGE mode. In the recent version of the VVC standard under development, addition Inter prediction modes are also considered in addition to the (regular) MERGE mode and the AFFINE MERGE mode. Such additional inter prediction modes currently being considered are a Multi-Hypothesis Intra Inter (MHII) MERGE mode, a TRIANGLE MERGE mode, and a Merge with Motion Vector Difference (MMVD) MERGE mode, which are described below.

It is understood that according to variants of those first few embodiments, one or more of the additional inter prediction modes may be used in addition to, or instead of, the MERGE mode or AFFINE MERGE mode, and an index (or a flag or information) for the one or more of the additional inter prediction modes may be signalled (encoded or decoded) using the same technique as either one of the MERGE mode or the AFFINE MERGE mode.

Multi-Hypothesis Intra Inter (MHII) MERGE Mode

The Multi-Hypothesis Intra Inter (MHII) MERGE mode is a hybrid which combines the regular MERGE mode with the Intra mode. A block predictor of this mode is obtained as an average between a (regular) MERGE mode block predictor and an Intra mode block predictor. The obtained block predictor is then added to a residual of the current block to obtain the reconstructed block. In order to obtain this MERGE mode block predictor, the MHII MERGE mode uses the same number of candidates as the MERGE mode and uses the same MERGE candidate derivation process. So an index signalling for the MHII MERGE mode can use the same technique as the index signalling for the MERGE mode. Moreover, this mode is enabled only for non-Skip mode encoded/decoded blocks. So when the current CU is encoded/decoded in a Skip mode, the MHII is unavailable for use in the encoding/decoding process.

Triangle MERGE Mode

The TRIANGLE MERGE mode is a type of a bi-prediction mode which uses a triangular shape based motion compensation. FIG. 25(a) and FIG. 25(b) illustrate different partition configurations used for its block predictor generation. The block predictor is obtained from a first triangle (a first block predictor 2501 or 2511) and a second triangle (a second block predictor 2502 or 2512) in the block. There are two different configurations used for this block predictor generation. For the first one, a division/split between the triangular portions/regions (from which the two block predictor candidates are associated with) is from the top left corner to the bottom right corner as depicted in FIG. 25(a). For the second one, the division/split between the triangular regions (from which the two block predictor candidates are associated with) is from the top right corner to the bottom left corner as depicted in FIG. 25(b). In addition, samples around the boundary between the triangular regions are filtered with a weighted average where the weight depends on the sample position (e.g. distance from the boundary). An independent TRIANGLE MERGE candidates list is generated, and an index signalling for the TRIANGLE MERGE mode can use an accordingly modified technique to those for an index signalling in the MERGE mode or AFFINE MERGE mode.

Merge with Motion Vector Difference (MMVD) MERGE Mode

The MMVD MERGE mode is a special type of a regular MERGE mode candidate derivation, which generates an independent MMVD MERGE candidates list. The selected MMVD MERGE candidate, for the current CU, is obtained by adding an offset value to one motion vector component (mvx or mvy) of a MMVD MERGE candidate. The offset value is added to the component of a motion vector from the first list L0 or the second list L1 depending on the configuration of these reference frames (e.g. both backward, both forward or forward and backward). The selected MMVD MERGE candidate is signalled using an index. The offset value is signalled using a distance index between 8 possible preset distances (¼-pel, ½-pel,1-pel, 2-pel, 4-pel, 8-pel, 16-pel, 32-pel) and a direction index giving the x or y axis and the sign of the offset. So the index signalling for the MMVD MERGE mode can use the same technique as the index signalling for the MERGE mode, or even AFFINE MERGE mode.

Embodiments

Embodiments of the invention will now be described with reference to remaining Figures. It should be noted that the embodiments may be combined unless explicitly stated otherwise; for example certain combinations of embodiments may improve coding efficiency at increased complexity, but this may be acceptable in certain use cases.

First Embodiment

As noted above, in the VTM reference software, ATMVP is signalled as a Merge candidate inserted in the list of Merge candidates. ATMVP can be enabled or disabled for a whole sequence (at SPS level). When ATMVP is disabled, the maximum number of Merge candidates is 5. When ATMVP is enabled, the maximum number of Merge candidates is increased by one from 5 to 6.

In the encoder, the list of Merge candidates is generated using the method of FIG. 13. One Merge candidate is selected from the list of Merge candidates, for example based on a rate-distortion criterion. The selected Merge candidate is signalled to the decoder in the bitstream using a syntax element called the Merge index.

In the current VTM reference software, the manner of coding the Merge index is different depending on whether ATMVP is enabled or disabled.

FIG. 10(a) illustrates the coding of the Merge index when ATMVP is not enabled at SPS level. The 5 Merge candidates Cand0, Cand1, Cand2, Cand3 and Cand4 are coded 0, 10, 110, 1110 and 1111 respectively. This corresponds to a unary max coding. In addition, the first bit is coded by CABAC using a single context and the other bits are bypass coded.

FIG. 10(b) illustrates the coding of the Merge index when ATMVP is enabled. The 6 Merge candidates Cand0, Cand1, Cand2, Cand3, Cand4, and Cand5 are coded 0, 10, 110, 1110, 11110 and 11111 respectively. In this case, all bits of the merge index (from the 1^(st) to the 5^(th) bit) are context coded by CABAC. Each bit has its own context and there are separate probability models for the different bits.

In the first embodiment of the present invention, as shown in FIG. 14, when ATMVP is included as a Merge candidate in the list of Merge candidates (for example, when ATMVP is enabled at SPS level) the coding of the Merge index is modified so that only the first bit of the Merge index is coded by CABAC using a single context. The context is set in the same manner as in the current VTM reference software when ATMVP is not enabled at SPS level, i.e. the other bits (from the 2^(nd) to the 5^(th) bit) are bypass coded. When ATMVP is not included as a Merge candidate in the list of Merge candidates (for example, when ATMVP is disabled at SPS level) there are 5 Merge candidates. Only the first bit of the Merge index is coded by CABAC using a single context. The context is set in the same manner as in the current VTM reference software when ATMVP is not enabled at SPS level. The other bits (from the 2^(nd) to the 4^(th) bit) are bypass decoded.

The decoder generates the same list of Merge candidates as the encoder. This may be accomplished by using the method of FIG. 13. When ATMVP is not included as a Merge candidate in the list of Merge candidates (for example, when ATMVP is disabled at SPS level) there are 5 Merge candidates. Only the first bit of the Merge index is decoded by CABAC using a single context. The other bits (from the 2^(nd) to the 4^(th) bit) are bypass decoded. In contrast to the current reference software, when ATMVP is included as a Merge candidate in the list of Merge candidates (for example, when ATMVP is enabled at SPS level), only the first bit of the Merge index is decoded by CABAC using a single context in the decoding of the Merge index. The other bits (from the 2^(nd) to the 5^(th) bit) are bypass decoded. The decoded merge index is used to identify the Merge candidate selected by the encoder from among the list of Merge candidates.

The advantage of this embodiment compared to the VTM2.0 reference software is a complexity reduction of the merge index decoding and decoder design (and encoder design) without impact on coding efficiency. Indeed, with this embodiment only 1 CABAC state is needed for the Merge index instead of 5 for the current VTM Merge index coding/decoding. Moreover, it reduces the worst-case complexity because the other bits are CABAC bypass coded which reduces the number of operations compared to coding all bits with CABAC.

Second Embodiment

In a second embodiment, all bits of the Merge index are CABAC coded but they all share the same context. There may be a single context as in the first embodiment, which in this case is shared among the bits. As a result, when ATMVP is included as a Merge candidate in the list of Merge candidates (for example, when ATMVP is enabled at SPS level), only one context is used, compared to 5 in the VTM2.0 reference software. The advantage of this embodiment compared to the VTM2.0 reference software is a complexity reduction of the merge index decoding and decoder design (and encoder design) without impact on coding efficiency.

Alternatively, as described below in connection with the third to sixteenth embodiments, a context variable may be shared among the bits so that two or more contexts are available but the current context is shared by the bits.

When ATMVP is disabled the same context is still used for all bits.

This embodiment and all subsequent embodiments can be applied even if ATMVP is not an available mode or is disabled.

In a variant of the second embodiment, any two or more bits of the Merge index are CABAC coded and share the same context. Other bits of the Merge index are bypass coded. For example, the first N bits of the Merge index may be CABAC coded, where N is two or more.

Third Embodiment

In the first embodiment the first bit of the Merge index was CABAC coded using a single context.

In the third embodiment, a context variable for a bit of the Merge index depends on the value of the Merge index of a neighbouring block. This allows more than one context for the target bit, with each context corresponding to a different value of the context variable.

The neighbouring block may be any block already decoded, so that its Merge index is available to the decoder by the time the current block is being decoded. For example, the neighbouring block may be any of the blocks A0, A1, A2, B0, B1, B2 and B3 shown in FIG. 6 b.

In a first variant, just the first bit is CABAC coded using this context variable.

In a second variant, the first N bits of the Merge index, where N is two or more, are CABAC coded and the context variable is shared among those N bits.

In a third variant, any N bits of the Merge index, where N is two or more, are CABAC coded and the context variable is shared among those N bits.

In a fourth variant, the first N bits of the Merge index, where N is two or more, are CABAC coded and N context variables are used for those N bits. Assuming the context variables have K values, K×N CABAC states are used. For example, in the present embodiment, with one neighbouring block, the context variable may conveniently have 2 values, e.g. 0 and 1. In other words 2N CABAC states are used.

In a fifth variant, any N bits of the Merge index, where N is two or more, are adaptive-PM coded and N context variables are used for those N bits.

The same variants are applicable to the fourth to sixteenth embodiments described hereinafter.

Fourth Embodiment

In the fourth embodiment, the context variable for a bit of the Merge index depends on the respective values of the Merge index of two or more neighbouring blocks. For example, a first neighbouring block may be a left block A0, A1 or A2 and a second neighbouring block may be an upper block B0, B1, B2 or B3. The manner of combining the two or more Merge index values is not particularly limited. Examples are given below.

The context variable may conveniently have 3 different values, e.g. 0, 1 and 2, in this case as there are two neighbouring blocks. If the fourth variant described in connection with the third embodiment is applied to this embodiment with 3 different values, therefore, K is 3 instead of 2. In other words 3N CABAC states are used.

Fifth Embodiment

In the fifth embodiment, the context variable for a bit of the Merge index depends on the respective values of the Merge index of the neighbouring blocks A2 and B3.

Sixth Embodiment

In the sixth embodiment, the context variable for a bit of the Merge index depends on the respective values of the Merge index of the neighbouring blocks A1 and B1. The advantage of this variant is alignment with the Merge candidates derivation. As a result, in some decoder and encoder implementations, memory access reductions can be achieved.

Seventh Embodiment

In the seventh embodiment, the context variable for a bit having bit position idx_num in the Merge Index of the current block is obtained according to the following formula:

ctxIdx=(Merge_index_left==idx_num)+(Merge_index_up==idx_num)

where Merge_index_left is the Merge index for a left block, Merge_index_up is the Merge index for an upper block, and the symbol == is the equality symbol.

When there are 6 Merge candidates, for example, 0<=idx_num<=5.

The left block may be the block A1 and the upper block may be the block B1 (as in the sixth embodiment). Alternatively, the left block may be the block A2 and the upper block may be the block B3 (as in the fifth embodiment).

The formula (Merge_index_left==idx_num) is equal to 1 if the Merge index for the left block is equal to idx_num. The following table gives the results of this formula (Merge_index_left==idx_num):

idx_num Merge_index_left 0 1 2 3 4 0 1 0 0 0 0 1 0 1 0 0 0 2 0 0 1 0 0 3 0 0 0 1 0 4 0 0 0 0 1 5 0 0 0 0 0

Of course the table of the formula (Merge_index_up==idx_num) is the same.

The following table gives the unary max code of each Merge index value and the relative bit position for each bit. This table corresponds to FIG. 10(b).

Unary max code Merge_index_left 0 1 2 3 4 0 0 1 1 0 2 1 1 0 3 1 1 1 0 4 1 1 1 1 0 5 1 1 1 1 1

If the left block is not a merge block or an affine merge block (i.e. coded using the Affine Merge mode) it is considered that the left block is not available. The same condition is applied for the upper block.

For example, when only the first bit is CABAC coded, the context variable ctxIdx is set equal to:

0 if no left and up/upper block has a merge index or if the left block Merge index is not the first index (i.e. not 0) and if the upper block Merge index is not the first index (i.e. not 0);

1 if one but not the other of the left and upper blocks has its merge index equal to the first index; and

2 if for each of the left and upper blocks the merge index is equal to the first index.

More generally, for a target bit at position idx_num which is CABAC coded, the context variable ctxIdx is set equal to:

0 if no left and up/upper block has a merge index or if the left block Merge index is not the i^(th) index (where i=idx_num) and if the upper block Merge index is not the i^(th) index;

1 if one but not the other of the left and upper blocks has its merge index equal to the the i^(th) index; and

2 if for each of the left and upper blocks the merge index is equal to the i^(th) index. Here, the i^(th) index means the first index when i=0, the second index when i=1, and so on.

Eighth Embodiment

In the eighth embodiment, the context variable for a bit having bit position idx_num in the Merge Index of the current block is obtained according to the following formula:

Ctx=(Merge_index_left>idx_num)+(Merge_index_up>idx_num) where Merge_index_left is the Merge index for a left block, Merge_index_up is the Merge index for an upper block, and the symbol > means “greater than”.

When there are 6 Merge candidates, for example, 0<=idx_num<=5.

The left block may be the block A1 and the upper block may be the block B1 (as in the sixth embodiment). Alternatively, the left block may be the block A2 and the upper block may be the block B3 (as in the fifth embodiment).

The formula (Merge_index_left>idx_num) is equal to 1 if the Merge index for the left block is greater than idx_num. If the left block is not a merge block or an affine merge block (i.e. coded using the Affine Merge mode) it is considered that the left block is not available. The same condition is applied for the upper block.

The following table gives the results of this formula (Merge_index_left>idx_num):

idx_num Merge_index_left 0 1 2 3 4 0 0 0 0 0 0 1 1 0 0 0 0 2 1 1 0 0 0 3 1 1 1 0 0 4 1 1 1 1 0 5 1 1 1 1 1

For example, when only the first bit is CABAC coded, the context variable ctxIdx is set equal to:

0 if no left and up/upper block has a merge index or if the left block Merge index is less than or equal to the first index (i.e. not 0) and if the upper block Merge index is less than or equal to the first index (i.e. not 0);

1 if one but not the other of the left and upper blocks has its merge index greater than the first index; and

2 if for each of the left and upper blocks the merge index is greater than the first index.

More generally, for a target bit at position idx_num which is CABAC coded, the context variable ctxIdx is set equal to:

0 if no left and up/upper block has a merge index or if the left block Merge index is less than the i^(th) index (where i=idx_num) and if the upper block Merge index is less than or equal to the i^(th) index;

1 if one but not the other of the left and upper blocks has its merge index greater than the i^(th) index; and

2 if for each of the left and upper blocks the merge index is greater than the i^(th) index.

The eighth embodiment provides a further coding efficiency increase over the seventh embodiment.

Ninth Embodiment

In the fourth to eighth embodiments, the context variable for a bit of the Merge index of the current block depended on the respective values of the Merge index of two or more neighbouring blocks.

In the ninth embodiment, the context variable for a bit of the Merge index of the current block depends on the respective Merge flags of two or more neighbouring blocks. For example, a first neighbouring block may be a left block A0, A1 or A2 and a second neighbouring block may be an upper block B0, B1, B2 or B3.

The Merge flag is set to 1 when a block is encoded using the Merge mode, and is set to 0 when another mode such as Skip mode or Affine Merge mode is used. Note that in VMT2.0 Affine Merge is a distinct mode from the basic or “classical” Merge mode. The Affine Merge mode may be signalled using a dedicated Affine flag. Alternatively, the list of Merge candidates may include an Affine Merge candidate, in which case the Affine Merge mode may be selected and signalled using the Merge index.

The context variable is then set to:

0 if neither the left nor the upper neighbouring block has its Merge flag set to 1;

1 if one but not the other of the left and upper neighbouring blocks has its Merge flag set to 1; and

2 if each of the left and upper neighbouring blocks has its Merge flag set to 1.

This simple measure achieves a coding efficiency improvement over VTM2.0. Another advantage, compared to the seventh and eighth embodiments, is a lower complexity because only the Merge flags and not the Merge indexes of the neighbouring blocks need to be checked.

In a variant, the context variable for a bit of the Merge index of the current block depends on the Merge flag of a single neighbouring block.

Tenth Embodiment

In the third to ninth embodiments, the context variable for a bit of the Merge index of the current block depended on Merge index values or Merge flags of one or more neighbouring blocks.

In the tenth embodiment, the context variable for a bit of the Merge index of the current block depends on the value of the Skip flag for the current block (current Coding Unit, or CU). The Skip flag is equal to 1 when the current block uses the Merge Skip mode, and is equal to 0 otherwise.

The Skip flag is a first example of another variable or syntax element already been decoded or parsed for the current block. This other variable or syntax element preferably is an indicator of a complexity of the motion information in the current block. Since the occurrences of the Merge index values depend on the complexity of the motion information a variable or syntax element such as the Skip flag is generally correlated with the merge index value.

More specifically, the Merge Skip mode is generally selected for static scenes or scenes involving constant motion. Consequently, the merge index value is generally lower for the Merge Skip mode than for the classical merge mode which is used to encode an inter prediction which contains a block residual. This occurs generally for more complex motion. However, the selection between these modes is also often related to the quantization and/or the RD criterion.

This simple measure provides a coding efficiency increase over VTM2.0. It is also very simple to implement as it does not involve neighbouring blocks or checking Merge index values.

In a first variant, the context variable for a bit of the Merge index of the current block is simply set equal to the Skip flag of the current block. The bit may be the first bit only. Other bits are bypass coded as in the first embodiment.

In a second variant, all bits of the Merge index are CABAC coded and each of them has its own context variable depending on the Merge flag. This requires 10 states of probabilities when there are 5 CABAC-coded bits in the Merge index (corresponding to 6 Merge candidates).

In a third variant, to limit the number of states, only N bits of the Merge index are CABAC coded, where N is two or more, for example the first N bits. This requires 2N states. For example, when the first 2 bits are CABAC coded, 4 states are required.

Generally, in place of the Skip flag, it is possible to use any other variable or syntax element that has already been decoded or parsed for the current block and that is an indicator of a complexity of the motion information in the current block.

Eleventh Embodiment

The eleventh embodiment relates to Affine Merge signalling as described previously with reference to FIGS. 11(a), 11(b) and 12.

In the eleventh embodiment, the context variable for a CABAC coded bit of the Merge index of the current block (current CU) depends on the Affine Merge candidates, if any, in the list of Merge candidates. The bit may be the first bit only of the Merge index, or the first N bits, where N is two or more, or any N bits. Other bits are bypass coded.

Affine prediction is designed for compensating complex motion. Accordingly, for complex motion the merge index generally has higher values than for less complex motion. It follows that if the first Affine Merge candidate is far down the list, or if there is no Affine Merge candidate at all, the merge index of the current CU is likely to have a small value.

It is therefore effective for the context variable to depend on the presence and/or position of at least one Affine Merge candidate in the list.

For example, the context variable may be set equal to:

1 if A1 is affine, 2 if B1 is affine, 3 if B0 is affine, 4 if A0 is affine, 5 if B2 is affine, and 0 if no neighbouring block is affine.

When the Merge index of the current block is decoded or parsed the affine flags of the Merge candidates at these positions have already been checked. Consequently, no further memory accesses are needed to derive the context for the Merge index of the current block.

This embodiment provides a coding efficiency increase over VTM2.0. No additional memory accesses are required since step 1205 already involves checking the neighbouring CU affine modes.

In a first variant, to limit the number of states, the context variable may be set equal to:

0 if no neighbouring block is affine, or if A1 or B1 is affine, and 1 if B0, A0 or B2 is affine.

In a second variant, to limit the number of states, the context variable may be set equal to: 0 if no neighbouring block is affine, 1 if A1 or B1 is affine, and 2 if B0, A0 or B2 is affine.

In a third variant, the context variable may be set equal to:

1 if A1 is affine, 2 if B1 is affine, 3 if B0 is affine, 4 if A0 or B2 is affine, and 0 if no neighbouring block is affine.

Please note that these positions are already checked when the merge index is decoded or parsed because the affine flag decoding depends on these positions. Consequently, there is no need for additional memory access to derive the Merge index context which is coded after the affine flag.

Twelfth Embodiment

In the twelfth embodiment, signalling the affine mode comprises inserting affine mode as a candidate motion predictor.

In one example of the twelfth embodiment, the Affine Merge (and Affine Merge Skip) is signalled as a Merge candidate (i.e. as one of the Merge candidates for use with the classical Merge mode or the classical Merge Skip mode). In that case the modules 1205, 1206 and 1207 of FIG. 12 are removed. In addition, not to affect the coding efficiency of the Merge mode, the maximum possible number of Merge candidates is incremented. For example, in the current VTM version this value is set equal to 6, so with if applying this embodiment to the current version of VTM, the value would be 7.

The advantage is a design simplification of the syntax element of the Merge modes because fewer syntax elements need to be decoded. In some circumstances, a coding efficiency improvement/change can be observed.

Two possibilities to implement this example will now be described:

The Merge index for the Affine Merge candidate always has the same position inside the list whatever the value of the other Merge MV. The position of a candidate motion predictor indicates its likelihood of being selected and as such if it is placed higher up the list (a lower index value), that motion vector predictor is more likely to be selected.

In the first example, the Merge index for the Affine Merge candidate always has the same position inside the list of Merge candidates. This means that it has a fixed “Merge idx” value. For example, this value can be set equal to 5, as the Affine Merge mode should represent a complex motion which is not the most probable content. The additional advantage of this embodiment is that when the current block is parsed (decoding/reading of the syntax element only but not decoding the data itself), the current block can be set as affine block. Consequently the value can be used to determine the CABAC context for the affine flag which is used for AMVP. So the conditional probabilities should be improved for this affine flag and the coding efficiency should be better.

In a second example, the Affine Merge candidate is derived with other Merge candidates. In this example, a new Affine Merge candidate is added into the list of Merge candidates (for the classical Merge mode or the classical Merge Skip mode). FIG. 16 illustrates this example. Compared to FIG. 13, the Affine Merge candidate is the first affine neighbouring block from A1, B1, B0, A0, and B2 (1917). If the same condition as 1205 of FIG. 12 is valid (1927), the motion vector field produced with the affine parameters is generated to obtain the Affine Merge candidate (1929). The list of initial Merge candidates can have 4, 5, 6 or 7 candidates according to the usage of ATMVP, Temporal and Affine Merge candidates.

The order between all these candidate is important as more likely candidates should be processed first to ensure they are more likely to make the cut of motion vector candidates—a preferred ordering is the following:

A1, B1, B0, A0, AFFINE MERGE, ATMVP, B2, TEMPORAL, Combined Zero_MV.

It is important to note that the Affine Merge candidate is positioned before the ATMVP candidate but after the four main neighbouring blocks. An advantage to setting the Affine Merge candidate before the ATMVP candidate is a coding efficiency increase, as compared to setting it after the ATMVP and the temporal predictor candidate. This coding efficiency increase depends on the GOP (group of pictures) structure and Quantization Parameter (QP) setting of each picture in the GOP. But for the most use GOP and QP setting this order gives a coding efficiency increase.

A further advantage of this solution is a clean design of the classical Merge and classical Merge Skip modes (i.e. the Merge modes with additional candidates such as ATMVP or Affine Merge candidate) for both syntax and derivation process. Moreover, the Merge index for the Affine Merge candidate can change according to the availability or value (duplicate check) of previous candidates in the list of Merge candidates. Consequently an efficient signalization can be obtained.

In a further example, the Merge index for the Affine Merge candidate is variable according to one or several conditions.

For example, the Merge index or the position inside the list associated with the Affine Merge candidate changes according to a criterion. The principle is to set a low value for the Merge index corresponding to the Affine Merge candidate when the Affine Merge candidate has a high probability of being selected (and a higher value when there is low probability to be selected).

In the twelfth embodiment, the Affine Merge candidate has a Merge index value. To improve the coding efficiency of the Merge index, it is effective to make the context variable for a bit of the Merge index dependent on the affine flags for neighbouring blocks and/or for the current block.

For example, the context variable may be determined using the following formula:

ctxIdx=IsAffine(A1)+IsAffine(B1)+IsAffine(B0)+IsAffine(A0)+IsAffine(B2)

The resulting context value may have the value 0, 1, 2, 3, 4 or 5.

The affine flags increase the coding efficiency.

In a first variant, to involve fewer neighbouring blocks, ctxIdx=IsAffine(A1)+IsAffine(B1). The resulting context value may have the value 0, 1, or 2.

In a second variant, also involving fewer neighbouring blocks, ctxIdx=IsAffine(A2)+IsAffine(B3). Again, the resulting context value may have the value 0, 1, or 2.

In a third variant, involving no neighbouring blocks, ctxIdx=IsAffine(current block). The resulting context value may have the value 0 or 1.

FIG. 15 is a flow chart of the partial decoding process of some syntax elements related to the coding mode with the third variant. In this figure, the Skip flag (1601), the prediction mode (1611), the Merge flag (1603), the Merge Index (1608) and the affine flag (1606) can be decoded. This flow chart is similar to that of FIG. 12, described hereinbefore, and a detailed description is therefore omitted. The difference is that the Merge index decoding process takes into account of the affine flag so that it is possible to use the affine flag, which is decoded before the Merge index, when obtaining a context variable for the Merge index, which is not the case in VTM 2.0. In VTM2.0 the affine flag of the current block cannot be used to obtain the context variable for the Merge index because it always has the same value ‘0’.

Thirteenth Embodiment

In the tenth embodiment, the context variable for a bit of the Merge index of the current block depends on the value of the Skip flag for the current block (current Coding Unit, or CU). In the thirteenth embodiment, instead of using the Skip flag value directly to derive the context variable for the target bit of the Merge index, the context value for the target bit is derived from the context variable used for coding the Skip flag of the current CU. This is possible because the Skip flag is itself CABAC coded and therefore has a context variable. Preferably, the context variable for the target bit of the Merge index of the current CU is set equal to (copied from) the context variable used for coding the Skip flag of the current CU. The target bit may be the first bit only. Other bits may be bypass coded as in the first embodiment.

The context variable for the Skip flag of the current CU is derived in the manner prescribed in VTM2.0. The advantage of this embodiment compared to the VTM2.0 reference software is a complexity reduction of the Merge index decoding and decoder design (and encoder design) without impact on the coding efficiency. Indeed, with this embodiment, at the minimum only 1 CABAC state is needed for coding the Merge index instead of 5 for the current VTM Merge index coding (encoding/decoding). Moreover, it reduces the worst-case complexity because the other bits are CABAC bypass coded which reduces the number of operations compared to coding all bits with CABAC.

Fourteenth Embodiment

In the thirteenth embodiment, the context variable/value for the target bit was derived from the context variable for the Skip flag of the current CU. In the fourteenth embodiment, the context value for the target bit is derived from the context variable for the affine flag of the current CU.

This is possible because the affine flag is itself CABAC coded and therefore has a context variable. Preferably, the context variable for the target bit of the Merge index of the current CU is set equal to (copied from) the context variable for the affine flag of the current CU. The target bit may be the first bit only. Other bits are bypass coded as in the first embodiment.

The context variable for the affine flag of the current CU is derived in the manner prescribed in VTM2.0.

The advantage of this embodiment compared to the VTM2.0 reference software is a complexity reduction in the Merge index decoding and decoder design (and encoder design) without impact on coding efficiency. Indeed, with this embodiment, at the minimum only 1 CABAC state is needed for the Merge index instead of 5 for the current VTM Merge index coding (encoding/decoding). Moreover, it reduces the worst-case complexity because the other bits are CABAC bypass coded which reduces the number of operations compared to coding all bits with CABAC.

Fifteenth Embodiment

In several of the foregoing embodiments, the context variable had more than 2 values, for example the three values 0, 1 and 2. However, to reduce the complexity, and reduce the number of states to be handled, it is possible to cap the number of permitted context-variable values at 2, e.g. 0 and 1. This can be accomplished, for example, by changing any initial context variable having the value 2 to 1. In practice, this simplification has no or only a limited impact on the coding efficiency.

Combinations of Embodiments and Other Embodiments

Any two or more of the foregoing embodiments may be combined.

The preceding description has focussed on the encoding and decoding of the Merge index. For example, the first embodiment involves generating a list of Merge candidates including an ATMVP candidate (for the classical Merge mode or the classical Merge Skip mode, i.e. the non-Affine Merge mode or the non-Affine Merge Skip mode); selecting one of the Merge candidates in the list; and generating a Merge index for the selected Merge candidate using CABAC coding, one or more bits of the Merge index being bypass CABAC coded. In principle, the present invention can be applied to modes other than the Merge modes (e.g. an Affine Merge mode) that involve generating a list of motion information predictor candidates (e.g. a list of Affine Merge candidates or motion vector predictor (MVP) candidates); selecting one of the motion information predictor candidates (e.g. MVP candidates) in the list; and generating an identifier or an index for the selected motion information predictor candidate in the list (e.g. the selected Affine Merge candidate or the selected MVP candidate for predicting the motion vector of the current block). Thus, the present invention is not limited to the Merge modes (i.e. the classical Merge mode and the classical Merge Skip mode) and the index to be encoded or decoded is not limited to the Merge index. For example, in the development of VVC, it is conceivable that the techniques of the foregoing embodiments could be applied to (or extended to) a mode other than the Merge modes, such as the AMVP mode of HEVC or its equivalent mode in VVC or the Affine Merge mode. The appended claims are to be interpreted accordingly.

As discussed, in the foregoing embodiments, one or more motion information candidate (e.g. motion vector) for the Affine Merge modes (Affine Merge or Affine Merge Skip mode) and/or one or more affine parameter are obtained from the first neighbouring block which is affine coded among spatially neighbouring blocks (e.g. at positions A1, B1, B0, A0, B2) or temporally associated blocks (e.g. a “Center” block with a collocated block or a spatial neighbour thereof such as “H”). These positions are depicted in FIGS. 6a and 6b . To enable this obtaining (e.g. deriving or sharing or “merging”) of the one or more motion information and/or affine parameter between a current block (or a group of sample/pixel values that are currently being encoded/decoded, e.g. a current CU) and a neighbouring block (either spatially neighbouring or temporally associated to the current block), one or more Affine Merge candidate are added to the list of Merge candidates (i.e. classical Merge mode candidates) so that when the selected Merge candidate (which is then signalled using a Merge index, for example using a syntax element such as “merge_idx” in HEVC or a functionally equivalent syntax element thereof) is the Affine Merge candidate, the current CU/block is encoded/decoded using the Affine Merge mode with the Affine Merge candidate.

As mentioned above, such one or more Affine Merge candidates for obtaining (e.g. deriving or sharing) of the one or more motion information for the Affine Merge mode and/or affine parameter can also be signalled using a separate list (or a set) of Affine Merge candidates (which can be the same or different from the list of Merge candidates used for the classical Merge mode).

According to an embodiment of the present invention, when the techniques of the foregoing embodiments are applied to the Affine Merge mode, the list of Affine Merge candidates may be generated using the same technique as the motion vector derivation process for the classical Merge mode as shown in, and described in relation to, FIG. 8, or as the Merge candidates derivation process shown in, and described in relation to, FIG. 13. Advantage of sharing the same technique to generate/compile this list of Affine Merge candidates (for the Affine Merge mode or the Affine Merge Skip mode) and the list of Merge candidates (for the classical Merge mode or the classical Merge Skip mode) is reduction in complexity in the encoding/decoding process when compared with having separate techniques.

It is understood that, to achieve similar advantages, according to other embodiments similar techniques are applied to other inter prediction modes which require signalling a selected motion information predictor (from a plurality of candidates).

According to another embodiment, a separate technique shown below in relation to FIG. 24 may be used to generate/compile the list of Affine Merge candidates.

FIG. 24 is a flow chart illustrating an Affine Merge candidate derivation process for the Affine Merge mode (the Affine Merge mode and the Affine Merge Skip mode). In a first step of the derivation process, five block positions are considered (2401 to 2405) for obtaining/deriving spatial Affine Merge candidates 2413. These positions are the spatial positions depicted in FIG. 6a (and FIG. 6b ) with references A1, B1, B0, A0, and B2. In a following step, the availability of the spatial motion vectors is checked and it is determined whether each of Inter mode coded blocks associated with each position A1, B1, B0, A0, and B2 are coded with the affine mode (e.g. using any one of Affine Merge, Affine Merge Skip or Affine AMVP mode) (2410). At most five motion vectors (i.e. spatial Affine Merge candidates) are selected/obtained/derived. A predictor is considered as available if it exists (e.g. there is information for obtaining/deriving a motion vector associated with that position) and if the block is not INTRA coded and if the block is affine (i.e. coded using the Affine mode).

Then Affine motion information is derived/obtained (2411) for each available block position (2410). This derivation is performed for the current block based on the affine model (and its affine model parameters discussed in relation to FIGS. 11(a) and 11(b), for example) of the block position. Then a pruning process (2412) is applied to remove candidates which give the same affine motion compensation (or which have the same affine model parameters) as another one previously added to the list.

At the end of this stage, the list of spatial Affine Merge candidates comprises up to five candidates.

If the number (Nb_Cand) of candidates is strictly less (2426) than the maximum number of candidates (here, Max_Cand is a value which is signalled in the bitstream slice header and is equal to five for Affine Merge mode but can be different/variable depending on the implementation).

Then the constructed Affine Merge candidates (i.e. additional Affine Merge candidates which are generated to provide some diversity as well as approach the target number, playing a similar role as the combined bi-predictive Merge candidates in HEVC for example) are generated (2428). These constructed Affine Merge candidates are based on the motion vectors associated with neighbouring spatial and temporal positions of the current block. First, the control points are defined (2418, 2419, 2420, 2421) in order to generate the motion information for generating an affine model. Two of these control points correspond to v₀ and v₁ of FIGS. 11(a) and 11(b), for example. These four control points correspond to the four corners of the current block.

The control point top left (2418)'s motion information is obtained from (e.g. by equating it to) the motion information of the block position at the position B2 (2405) if it exists and if this block is coded with an INTER mode (2414). Otherwise, the control point top left (2418)'s motion information is obtained from (e.g. by equating it to) the motion information of the block position at the position B3 (2406) (as depicted in FIG. 6b ) if it exists and if this block is coded with an INTER mode (2414) and if it is not the case, the control point top left (2418)'s motion information is obtained from (e.g. equated to) the motion information of the block position at the position A2 (2407) (as depicted in FIG. 6b ) if it exists and if this block is coded with an INTER mode (2414). When no block is available for this control point it is considered as being unavailable (non-available).

The control point top right (2419)'s motion information is obtained from (e.g. equated to) the motion information of the block position at the position B1 (2402) if it exists and if this block is coded with an INTER mode (2415). Otherwise, the control point top right (2419)'s motion information is obtained from (e.g. equated to) the motion information of the block position at the position B0 (2403) if it exists and if this block is coded with an INTER mode (2415). When no block is available for this control point it is considered as being unavailable (non-available).

The control point bottom left (2420)'s motion information is obtained from (e.g. equated to) the motion information of the block position at the position A1 (2401) if it exists and if this block is coded with an INTER mode (2416). Otherwise, the control point bottom left (2420)'s motion information is obtained from (e.g. equated to) the motion information of the block position at the position A0 (2404) if it exists and if this block is coded with an INTER mode (2416). When no block is available for this control point it is considered as being unavailable (non-available).

The control point bottom right (2421)'s motion information is obtained from (e.g. equated to) the motion information of the temporal candidate, e.g. the collocated block position at the position H (2408) (as depicted in FIG. 6a ) if it exists and if this block is coded with an INTER mode (2417). When no block is available for this control point it is considered as being unavailable (non-available).

Based on these control points, up to 10 constructed Affine Merge candidates can be generated (2428). These candidates are generated based on an affine model with 4, 3 or 2 control points. For example, the first constructed Affine Merge candidate may be generated using the 4 control points. Then the 4 following constructed Affine Merge candidates are the 4 possibilities which can be generated using 4 different sets of 3 control points (i.e. 4 different possible combinations of a set containing 3 out of the 4 available control points). Then the other constructed Affine Merge candidates are those generated using different sets of 2 control points (i.e. different possible combinations of a set containing 2 of the 4 control points).

If the number (Nb_Cand) of candidates remains strictly less (2430) than the maximum number of candidates (Max_Cand) after adding these additional (constructed) Affine Merge candidates, other additional virtual motion information candidates such as zero motion vector candidates (or even combined bi-predictive merge candidates where applicable) are added/generated (2432) until the number of candidates in the list of Affine Merge candidates reaches the target number (e.g. maximum number of candidates).

At the end of this process, the list or set of Affine Merge mode candidates (i.e. a list or set of candidates for the Affine Merge modes, which are the Affine Merge mode and the Affine Merge Skip mode) is generated/built (2434). As illustrated in FIG. 24, the list or set of Affine Merge (motion vector predictor) candidates is built/generated (2434) from a subset of spatial candidates (2401 to 2407) and a temporal candidate (2408). It is understood that according to embodiments of the invention, other Affine Merge candidate derivation processes with different order for checking availability, pruning process, or number/type of potential candidates (e.g. ATMVP candidate may be also added in a similar manner to the Merge candidate list derivation process in FIG. 13 or FIG. 16) may also be used to generate the list/set of Affine Merge candidates.

Following embodiment illustrates how a list (or a set) of Affine Merge candidates can be used to signal (e.g. encode or decode) a selected Affine Merge candidate (which can be signalled using a Merge index used for the Merge mode or a separate Affine Merge index specifically for use with the Affine Merge mode).

In the following embodiment: a MERGE mode (i.e. a merge mode other than an AFFINE MERGE mode defined later, in other words classical non-Affine Merge mode or classical non-Affine Merge Skip mode) is a type of merge mode where motion information of either spatially neighbouring or temporally associated block is obtained for (or derived for or shared with) the current block, a MERGE mode predictor candidate (i.e. a Merge candidate) is information regarding one or more spatially neighbouring or temporally associated block from which the current block can obtain/derive the motion information in the MERGE mode, a MERGE mode predictor is a selected MERGE mode predictor candidate whose information is used when predicting the motion information of the current block and during the signalling in the MERGE mode (e.g. encoding or decoding) process an index (e.g. a MERGE index) identifying the MERGE mode predictor from a list (or set) of MERGE mode predictor candidates is signalled, an AFFINE MERGE mode is a type of merge mode where motion information of either spatially neighbouring or temporally associated block is obtained for (derived for or shared with) the current block so that motion information and/or affine parameter for Affine mode processing (or Affine motion model processing) of the current block can make use of this obtained/derived/shared motion information, an AFFINE MERGE mode predictor candidate (i.e. an Affine Merge candidate) is information regarding one or more spatially neighbouring or temporally associated block from which the current block can obtain/derive the motion information in the AFFINE MERGE mode, and an AFFINE MERGE mode predictor is a selected AFFINE MERGE mode predictor candidate whose information is usable in the Affine motion model when predicting the motion information of the current block and during the signalling in the AFFINE MERGE mode (e.g encoding or decoding) process an index (e.g. an AFFINE MERGE index) identifying the AFFINE MERGE mode predictor from a list (or set) of AFFINE MERGE mode predictor candidates is signalled. It is understood that in the following embodiment, the AFFINE MERGE mode is a merge mode which has its own AFFINE MERGE index (an identifier which is a variable) for identifying one AFFINE MERGE mode predictor candidate from a list/set of candidates (also known as an “Affine Merge list” or a “subblock Merge list”), as opposed to having a single index value associated with it, wherein the AFFINE MERGE index is signalled to identify that particular AFFNE MERGE mode predictor candidate.

It is understood that in the following embodiment, the “MERGE mode” refers to either one of the classical Merge mode or the classical Merge Skip mode in HEVC/JEM/VTM or any functionally equivalent mode, provided that such obtaining (e.g. deriving or sharing) of the motion information and signalling of the Merge index as described above is used in said mode. The “AFFINE MERGE mode” also refers to either one of the Affine Merge mode or the Affine Merge Skip mode (if present and uses such obtaining/deriving) or any other functionally equivalent mode, provided the same features are used in said mode.

Sixteenth Embodiment

In the sixteenth embodiment, a motion information predictor index for identifying an AFFINE MERGE mode predictor (candidate) from the list of AFFINE MERGE candidates is signalled using CABAC coding, wherein one or more bits of the motion information prediction index is bypass CABAC coded.

According to a first variant of the embodiment, at an encoder, a motion information predictor index for an AFFINE MERGE mode is encoded by: generating a list of motion information predictor candidates; selecting one of the motion information predictor candidates in the list as an AFFINE MERGE mode predictor; and generating a motion information predictor index for the selected motion information predictor candidate using CABAC coding, one or more bits of the motion information predictor index being bypass CABAC coded. Data indicating an index for this selected motion information predictor candidate is then included in a bitstream. A decoder then, from the bitstream including this data, decodes the motion information predictor index for the AFFINE MERGE mode by: generating a list of motion information predictor candidates; decoding the motion information predictor index using CABAC decoding, one or more bits of the motion information predictor index being bypass CABAC decoded; when the AFFINE MERGE mode is used, using the decoded motion information predictor index to identify one of the motion information predictor candidates in the list as an AFFINE MERGE mode predictor.

According to a further variant of the first variant, one or more of the motion information predictor candidates in the list is also selectable as a MERGE mode predictor when a MERGE mode is used so that when the MERGE mode is used, the decoder can use the decoded motion information predictor index (e.g. MERGE index) to identify one of the motion information predictor candidates in the list as a MERGE mode predictor. In this further variant, an AFFINE MERGE index is used to signal an AFFINE MERGE mode predictor (candidate), and the AFFINE MERGE index signalling is implemented using an index signalling that is analogous to the MERGE index signalling according to any one of the first to fifteenth embodiments or the MERGE index signalling used in the current VTM or HEVC.

In this variant, when the MERGE mode is used the MERGE index signalling can be implemented using the MERGE index signalling according to any one of the first to fifteenth embodiment or the MERGE index signalling used in the current VTM or HEVC. In this variant, the AFFINE MERGE index signalling and the MERGE index signalling can use different index signalling schemes. The advantage of this variant is that it achieves a better coding efficiency by using an efficient index coding/signalling for both the AFFINE MERGE mode and MERGE mode. Further, in this variant separate syntax elements can be used for the MERGE index (such as “Merge idx[ ][ ]” in HEVC or functional equivalent thereof) and the AFFINE MERGE index (such as “A_Merge_idx[ ][ ]”). This enables the MERGE index and the AFFINE MERGE index to be signalled (encoded/decoded) independently.

According to yet another further variant, when the MERGE mode is used and one of the motion information predictor candidates in the list is also selectable as the MERGE mode predictor, the CABAC coding uses the same context variable for at least one bit of the motion information predictor index (e.g. the MERGE index or the AFFINE MERGE index) of the current block for both modes, i.e. when the AFFINE MERGE mode is used and when the MERGE mode is used, so that the at least one bit of the AFFINE MERGE index and the MERGE index share the same context variable. A decoder then, when the MERGE mode is used, uses the decoded motion information predictor index to identify one of the motion information predictor candidates in the list as the MERGE mode predictor, wherein the CABAC decoding uses the same context variable for the at least one bit of the motion information predictor index of the current block for both modes, i.e. when the AFFINE MERGE mode is used and when the MERGE mode is used.

According to a second variant of the embodiment, at an encoder, a motion information predictor index is encoded by: generating a list of motion information predictor candidates; when an AFFINE MERGE mode is used, selecting one of the motion information predictor candidates in the list as an AFFINE MERGE mode predictor; when a MERGE mode is used, selecting one of the motion information predictor candidates in the list as a MERGE mode predictor; and generating a motion information predictor index for the selected motion information predictor candidate using CABAC coding, one or more bits of the motion information predictor index being bypass CABAC coded. Data indicating an index for this selected motion information predictor candidate is then included in a bitstream. A decoder then, from the bitstream, decodes the motion information predictor index by: generating a list of motion information predictor candidates; decoding the motion information predictor index using CABAC decoding, one or more bits of the motion information predictor index being bypass CABAC decoded; when the AFFINE MERGE mode is used, using the decoded motion information predictor index to identify one of the motion information predictor candidates in the list as the AFFINE MERGE mode predictor; and when the MERGE mode is used, using the decoded motion information predictor index to identify one of the motion information predictor candidates in the list as the MERGE mode predictor.

According to a further variant of the second variant, the AFFINE MERGE index signalling and the MERGE index signalling use the same index signalling scheme according to any one of the first to fifteenth embodiment or the MERGE index signalling used in the current VTM or HEVC. An advantage of this further variant is a simple design during implementation, which also can lead to less complexity. In this variant, when the AFFINE MERGE mode is used, the encoder's the CABAC coding comprises using a context variable for at least one bit of the motion information predictor index (AFFINE MERGE index) of a current block, the context variable being separable from another context variable for the at least one bit of the motion information predictor index (MERGE index) when the MERGE mode is used; and data for indicating use of the AFFINE MERGE mode is included in a bitstream so that the context variables for the AFFINE MERGE mode and the MERGE mode can be distinguished (distinctly identified) for the CABAC decoding process. The decoder then obtains, from the bitstream, data for indicating use of the AFFINE MERGE mode in a bitstream; and when the AFFINE MERGE mode is used, the CABAC decoding uses this data to distinguish between the context variables for the AFFINE MERGE index and the MERGE index. Further, at the decoder, the data for indicating use of the AFFINE MERGE mode can also be used to generate a list (or set) of AFFINE MERGE mode predictor candidates when the obtained data indicates use of the AFFINE MERGE mode, or to generate a list (or set) of MERGE mode predictor candidates when the obtained data indicates use of the MERGE mode.

This variant enables both the MERGE index and the AFFINE MERGE index to be signalled using the same index signalling scheme whilst the MERGE index and the AFFINE MERGE index are still encoded/decoded independently from each other (e.g. by using separate context variables).

One way of using the same index signalling scheme is to use the same syntax element for both the AFFINE MERGE index and the MERGE index, that is the motion information predictor index for the selected motion information predictor candidate is encoded using the same syntax element for both cases, when the AFFINE MERGE mode is used and when the MERGE mode is used. Then at the decoder, the motion information predictor index is decoded by parsing, from the bitstream, the same syntax element regardless of whether the current block was encoded (and is being decoded) using the AFFINE MERGE mode or the MERGE mode.

FIG. 22 illustrates a partial decoding process of some syntax elements related to a coding mode (i.e. the same index signalling scheme) according to this variant of the sixteenth embodiment. This figure illustrates the signalling of the AFFINE MERGE index (2255—“Merge idx Affine”) for the AFFINE MERGE mode (2257: Yes) and of the MERGE index (2258—“Merge idx”) for the MERGE mode (2257: No) with the same index signalling scheme. It is understood that in some variants, the AFFINE MERGE candidate list can include an ATMVP candidate as in the Merge candidate list of the current VTM. The coding of the AFFINE MERGE index is similar to the coding of the MERGE index for the MERGE mode as depicted in FIG. 10(a), FIG. 10(b) or FIG. 14. In some variants, even if the AFFINE MERGE candidates derivation does not define an ATMVP merge candidate, the AFFINE MERGE index is coded as described in FIG. 10(b) when ATMVP is enabled for the MERGE mode with maximum of 5 other candidates (i.e. in total, 6 candidates) so that the maximum number of candidates in the AFFINE MERGE candidate list matches the maximum number of candidates in the MERGE candidate list. So, each bit of the AFFINE MERGE index has its own context. All context variables used for the bits of the Merge index signalling are independent of the context variables used for the bits of the AFFINE MERGE Index signalling.

According to a further variant, this same index signalling scheme shared by the MERGE index and the AFFINE MERGE index signalling uses CABAC coding on the first bin only as in the first embodiment. That is all bits except for a first bit of the motion information predictor index are bypass CABAC coded. In this further variant of the sixteenth embodiment, when ATMVP is included as a candidate in one of the list of MERGE candidates or the list of AFFINE MERGE candidates (for example, when ATMVP is enabled at SPS level) the coding of each index (i.e. the MERGE index or the AFFINE MERGE index) is modified so that only the first bit of the index is coded by CABAC using a single context variable as shown in FIG. 14. This single context is set in the same manner as in the current VTM reference software when ATMVP is not enabled at SPS level. The other bits (from the 2^(nd) to the 5^(th) bit or 4^(th) bit if there are only 5 candidates in the list) are bypass coded. When ATMVP is not included as a candidate in the list of MERGE candidates (for example, when ATMVP is disabled at SPS level), there are 5 MERGE candidates and 5 AFFINE MERGE candidates available for use. Only the first bit of the MERGE index for the MERGE mode is coded by CABAC using a first single context variable. And only the first bit of the AFFINE MERGE index for the AFFINE MERGE mode is coded by CABAC using a second single context variable. These first and second context variables are set in the same manner as in the current VTM reference software when ATMVP is not enabled at SPS level for both the MERGE index and the AFFINE MERGE index. The other bits (from the 2^(nd) to the 4^(th) bit) are bypass decoded.

The decoder generates the same list of MERGE candidates and the same list of AFFINE MERGE candidates as the encoder. This is accomplished by using, e.g. the method of FIG. 24. Although the same index signalling scheme is used for both the MERGE mode and the AFFINE MERGE mode, the affine flag (2256) is used to determine whether data currently being decoded is for the MERGE index or the AFFINE MERGE index so that the first and second context variables are separable (or distinguishable) from each other for the CABAC decoding process. That is, the affine flag (2256) is used during the index decoding process (i.e. used at step 2257) to determine whether to decode “merge idx 2258” or “merge idx Affine 2255”. When ATMVP is not included as a candidate in the list of MERGE candidates (for example, when ATMVP is disabled at SPS level) there are 5 MERGE candidates for both the lists of candidates (for the MERGE mode and the AFFINE MERGE mode). Only the first bit of the MERGE index is decoded by CABAC using the first single context variable. And only the first bit of the AFFINE MERGE index is decoded by CABAC using the second single context variable. All other bits (from the 2^(nd) to the 4^(th) bit) are bypass decoded. In contrast to the current reference software, when ATMVP is included as a candidate in the list of MERGE candidates (for example, when ATMVP is enabled at SPS level), only the first bit of the MERGE index is decoded by CABAC using the first single context variable in the decoding of the MERGE index and using the second single context variable in the decoding of the AFFINE MERGE index. The other bits (from the 2^(nd) to the 5^(th) bit or 4^(th) bit) are bypass decoded. The decoded index is then used to identify the candidate selected by the encoder from the corresponding list of candidates (i.e. the MERGE candidates or the AFFINE MERGE candidates).

The advantage of this variant is that use of the same index signalling scheme for both the MERGE index and the AFFINE MERGE index leads to a complexity reduction in the index decoding and the decoder design (and the encoder design) for implementing these two different modes, without significant impact on the coding efficiency. Indeed, with this variable only 2 CABAC states (one for each of the first and second single context variable) are needed for the index signalling, instead of 9 or 10 which would have been the case if all bits of the MERGE index and all bits of the AFFINE MERGE index are CABAC encoded/decoded. Moreover, it reduces the worst-case complexity because all other bits (apart from the first bit) are CABAC bypass coded, which reduces the number of operations needed during the CABAC encoding/decoding process compared to coding all bits with CABAC.

According to yet another further variant, the CABAC coding or decoding use the same context variable for at least one bit of the motion information predictor index of a current block for both when the AFFINE MERGE mode is used and when the MERGE mode is used. In this further variant, the context variable used for the first bit of the MERGE index and the first bit of the AFFINE MERGE index is independent of which index is being encoded or decoded, that is the first and second single context variables (from the previous variant) are not distinguishable/separable and are the one and the same single context variable. So contrary to the previous variant, the MERGE index and the AFFINE MERGE index share one context variable during the CABAC process. As shown in FIG. 23, the index signalling scheme is the same for both the MERGE index and the AFFINE MERGE index, i.e. only one type of index “Merge idx (2308)” is encoded or decoded for both modes. As far as the CABAC decoder is concerned, the same syntax element is used for both the MERGE index and the AFFINE MERGE index, and there is no need to distinguish them when considering context variables. So there is no need to use the Affine flag (2306) to determine whether the current block is encoded (to be decoded) in AFFINE MERGE mode or not as in step (2257) of FIG. 22, and there is no branching after step 2306 in FIG. 23 as only one index (“merge idx”) needs decoding. The affine flag is used to perform the motion information prediction with the AFFINE MERGE mode, i.e. during prediction process after the CABAC decoder has decoded the index (“merge idx”). Moreover, only the first bit of this index (i.e. the MERGE index and the AFFINE MERGE index) is coded by CABAC using one single context and the other bits are bypass coded as described for the first embodiment. So in this further variant, one context variable for the first bits of the MERGE index and the AFFINE MERGE index is shared by both the MERGE index and AFFINE MERGE index signalling. If the size of the lists of candidates are different for the MERGE index and the AFFINE MERGE index, then the maximum number of bits for signalling the relevant index for each case can also be different, i.e. they are independent from one another. So, the number of bypass coded bits can be adapted accordingly, if needed, according to the value of affine flag (2306), for example to enable parsing of data for the relevant index from the bitstream.

The advantage of this variant is a complexity reduction in the MERGE index and the AFFINE MERGE index decoding process and decoder design (and encoder design) without having a significant impact on the coding efficiency. Indeed, with this further variant, only 1 CABAC state is needed when signalling both the MERGE index and the AFFINE MERGE index, instead of CABAC states of the previous variant or 9 or 10. Moreover, it reduces the worst-case complexity because all other bits (apart from the first bit) are CABAC bypass coded, which reduces the number of operations needed during the CABAC encoding/decoding process compared to coding all bits with CABAC.

In the foregoing variants of this embodiment, the AFFINE MERGE index signalling and the MERGE index signalling may reduce the number of contexts and/or share one or more contexts as described in any of the first to fifteenth embodiment. The advantage of this is a complexity reduction from the reduction in the number of contexts needed to encode or decode these indexes.

In the foregoing variants of this embodiment, the motion information predictor candidate comprises information for obtaining (or deriving) one or more of: a direction, an identification for a list, a reference frame index, and a motion vector. Preferably the motion information predictor candidate comprises information for obtaining a motion vector predictor candidate. In a preferred variant, the motion information predictor index (e.g. AFFINE MERGE index) is used to signal an AFFINE MERGE mode predictor candidate, and the AFFINE MERGE index signalling is implemented using an index signalling that is analogous to the MERGE index signalling according to any one of the first to fifteenth embodiments or the MERGE index signalling used in the current VTM or HEVC (with the motion information predictor candidates for the AFFINE MERGE mode as the MERGE candidates).

In the foregoing variants of this embodiment, the generated list of motion information predictor candidates includes an ATMVP candidate as in the first embodiment or as in a variant of some of the other foregoing second to fifteenth embodiments. The ATMVP candidate maybe included in either one, or both, of the MERGE candidates list and the AFFINE MERGE candidates list. Alternatively, the generated list of motion information predictor candidates does not include the ATMVP candidate.

In the foregoing variants of this embodiment, the maximum number of candidates includable in the lists of candidates for the MERGE index and the AFFINE MERGE index is fixed. The maximum number of candidates includable in the lists of candidates for the MERGE index and the AFFINE MERGE index may be the same. Then data for determining (or indicating) the maximum number (or the target number) of motion information predictor candidates includable in the generated list of motion information predictor candidates is included, by the encoder, in the bitstream, and the decoder obtains, from the bitstream, the data for determining a maximum number (or a target number) of motion information predictor candidates includable in the generated list of motion information predictor candidates. This enables parsing, from the bitstream, of data for decoding the MERGE index or the AFFINE MERGE index. This data for determining (or indicating) the maximum number (or the target number) may be the maximum number (or the target number) itself when decoded, or it may enable the decoder to determine this maximum/target number in conjunction with other parameters/syntax elements, for example “five_minus_max_num_merge_cand” or “MaxNumMergeCand-1” used in HEVC or functionally equivalent parameters thereof.

Alternatively, if the maximum number (or the target number) of candidates in the lists of candidates for the MERGE index and the AFFINE MERGE index can vary or can be different (e.g. because use of the ATMVP candidate or any other optional candidate may be enabled or disabled for one list but not for the other list, or because the lists use different candidate list generation/derivation process), the maximum numbers (or the target numbers) of motion information predictor candidates includable in the generated list of motion information predictor candidates when the AFFINE MERGE mode is used and when the MERGE mode is used are determinable separately, and the encoder includes, in the bitstream, data for determining the maximum number(s)/target number(s). The decoder then obtains, from the bitstream, the data for determining the maximum/target number(s), and parses or decodes the motion information predictor index using the obtained data. The affine flag may then be used to switch between parsing or decoding of the MERGE index and the AFFINE MERGE index, for example.

As discussed earlier, one or more of the additional inter prediction modes (such as MHII MERGE mode, TRIANGLE MREGE Mode, and MMVD MERGE mode) may be used in addition to, or instead of, the MERGE mode or AFFINE MERGE mode, and an index (or a flag or information) for the one or more of the additional inter prediction modes may be signalled (encoded or decoded). Following embodiments relate to signalling of information (such as the index) for the additional inter prediction modes.

Seventeenth Embodiment

Signalling for all Inter prediction modes (including MERGE mode, AFFINE MERGE mode, MHII MERGE mode, Triangle MREGE Mode, and MMVD MERGE mode)

These plurality of inter prediction “MERGE” modes are signalled using data provided in the bitstream with their associated syntax (elements) according to the seventeenth embodiment. FIG. 26 illustrates a decoding process for inter prediction modes for a current CU (image portion or block) according to an embodiment of the invention. As described in relation to FIG. 12 (and its Skip flag at 1201), a first CU Skip flag is extracted from the bitstream (2601). If the CU is not Skip (2602), i.e. the current CU is not to be processed in the Skip mode, the pred mode flag (2603) and/or Merge flag (2606) are decoded to determine if the current CU is a Merge CU. If the current CU is to be processed in a Merge Skip (2602) or a Merge CU (2607), a MMVD_Skip_Flag or a MMVD_Merge_Flag is decoded (2608). If this flag is equal to 1 (2609) the current CU is decoded using the MMVD MERGE mode (i.e. with or in the MMVD MERGE mode), and consequently a MMVD MERGE index is decoded (2610) followed by a MMVD distance index (2611) and a MMVD direction index (2612). If the CU is not a MMVD merge CU (2609), a Merge sub block flag is decoded (2613). This flag is also denoted as an “Affine flag” in the previous description. If the current CU is to be processed in the AFFINE MERGE mode (also known as “sub block MERGE” mode) (2614), a Merge sub block index (i.e. AFFINE MERGE index) is decoded (2615). If the current CU is not to be processed in the AFFINE MERGE mode (2614) and also not in a Skip mode (2616), MHII MERGE flag is decoded (2620). If this block is to be processed in the MHII MERGE mode (2621), a regular MERGE index (2619) is decoded with its related Intra prediction mode (2622) for the MHII MERGE mode. Please note that the MHII MERGE mode is available only for the non-Skip “MERGE” mode and not for the Skip mode. If the MHII MERGE flag is equal to 0 (2621), or if the current CU is not to be processed in the AFFINE MERGE mode (2614) & in the Skip mode (2616), a TRIANGLE MERGE flag is decoded (2617). If this CU is to be processed in the TRIANGLE MERGE mode (2618), the TRIANGLE MERGE index is decoded (2623). If the current CU is not to be processed in the TRIANGLE MERGE mode (2618), the current CU is a regular MERGE mode CU, and the MERGE index is decoded.

Signalling of Each Merge Candidate

The MMVD MERGE Flag/Index Signalling

In a first variant of the seventeenth embodiment, only two initial candidates are available for use/selection in the MMVD MERGE mode. However, with 8 possible values for the distance index and 4 possible values for the direction index also being signalled with the bitstream, the number of potential candidates for use in the MMVD Merge mode at the decoder is 64 (2 candidates×8 distance index×4 direction index), each potential candidate being different from another (i.e. unique) when the initial candidates are different. These 64 potential candidates can be evaluated/compared for the MMVD MERGE mode at the encoder side, and the MMVD MERGE index (2610) for the selected initial candidate is then signalled with a unary max code. As only two initial candidates are used, this MMVD MERGE index (2610) corresponds to a flag. FIG. 27(a) illustrates the coding of this flag, which is CABAC coded using one context variable. It is understood that in another variant, different numbers of initial candidates, distance index values, and/or direction index values may be used instead with the signalling of the MMVD MERGE index being adapted accordingly (e.g. with at least one bit being CABAC coded using one context variable).

TRIANGLE MERGE Index Signalling

In the first variant of the seventeenth embodiment, a TRIANGLE MERGE index is signalled differently when compared with the index signalling for the other inter prediction modes. For the TRIANGLE MERGE mode, 40 possible permutations of candidates are available corresponding to the combination of 5 initial candidates and the 2 possible types of triangle (see FIG. 25(a) and FIG. 25(b), and the 2 possible first (2501 or 2511) and second (2502 or 2512) block predictors for each type of triangles). FIG. 27(b) illustrates a coding of an index for the TRIANGLE MERGE mode, i.e. the signalling of these candidates. The first bit (i.e. first bin) is CABAC decoded with one context. If this first bit is equal to 0, a second bit (i.e. second bin) is CABAC bypass decoded. If this second bit is equal to 0, the index corresponds to the first candidate in the list, i.e. index 0 (Cand 0). Otherwise (if the second bit is equal to 1), the index corresponds to the second candidate in the list, i.e. index 1 (Cand 1). If the first bit is equal to 1 an Exponential-Golomb code is extracted from the bitstream, with the Exponential-Golomb code representing an index for the selected candidate in the list, i.e. selected from index 2 (Cand 2) to index 39 (Cand 39).

It is understood that in another variant, different numbers of initial candidates may be used instead with the signalling of the TRIANGLE MERGE index being adapted accordingly (e.g. with at least one bit being CABAC coded using one context variable).

ATMVP in Affine Merge List

In a second variant of the seventeenth embodiment, the ATMVP is available as a candidate in the AFFINE MERGE candidate list (i.e. in the AFFINE MERGE mode—also known as the “Sub block Merge” mode). FIG. 28 illustrates the list for the AFFINE MERGE list derivation with this additional ATMVP candidate (2848). This figure is similar to FIG. 24 (which is described earlier) but with this additional ATMVP candidate (2848) being added to the list so any repetition of the detailed description is omitted here. It is understood that in another variant, different numbers of initial candidates may be used instead with the signalling of the TRIANGLE MERGE index being adapted accordingly (e.g. with at least one bit being CABAC coded using one context variable).

It is understood that in another variant, the ATMVP candidate may be added to a list of candidates for another inter prediction mode with its signalling of its index being adapted accordingly (e.g. with at least one bit being CABAC coded using one context variable).

It is also understood that although FIG. 26 provides a complete overview for the signalling for all inter prediction modes (i.e. MERGE mode, AFFINE MERGE mode, MHII MERGE mode, Triangle MREGE Mode, and MMVD MERGE mode), according to another variant only a subset of the inter prediction modes may be used instead.

Eighteenth Embodiment

According to the eighteenth embodiment, one or both of the TRIANGLE MERGE mode or the MMVD MERGE mode is available for use in the encoding or decoding process, and one or both of these inter prediction modes share a context variable (used with the CABAC coding) with another inter prediction mode when signalling its index/flag.

It is understood that in further variants of this or following embodiments, one or more of the inter prediction modes may use more than one context variables when signalling an index/flag thereof (e.g. the AFFINE MERGE mode may use 4 or 5 context variables, depending on whether an ATMVP candidate is also includable in the list, for its AFFINE MERGE index encoding/decoding process).

For example, before a variant of this or following embodiment is implemented, the total number of context variables for signalling all the bits of the indexes/flags for all inter prediction modes may be 7: (Regular) MERGE=1 (as shown in FIG. 10(a)); AFFINE MERGE=4 (as shown in FIG. 10(b) but with one less candidate, e.g. without an ATMVP candidate); TRIANGLE=MMVD=1; and MHII (if available for use)=0 (shared with Regular MERGE). Then, by implementing the variant, the total number of context variables for signalling all the bits of the indexes/flags for all inter prediction modes may be reduced to 5: (Regular) MERGE=1 (as shown in FIG. 10(a)); AFFINE MERGE=4 (as shown in FIG. 10(b) but with one less candidate, e.g. without an ATMVP candidate); and TRIANGLE=MMVD=MHII (if available for use)=0 (shared with Regular MERGE).

In another example, before this variant is implemented, the total number of context variables for signalling all the bits of the indexes/flags for all inter prediction modes may be 4: (Regular) MERGE=AFFINE MERGE=TRIANGLE=MMVD=1 (as shown in FIG. 10(a)); and MHII (if available for use)=0 (shared with Regular MERGE). Then, by implementing this variant, the total number of context variables for signalling all the bits of the indexes/flags for all inter prediction modes is reduced to 2: (Regular) MERGE=AFFINE MERGE=1 (as shown in FIG. 10(a)); and TRIANGLE=MMVD=MHII (if available for use)=0 (shared with Regular MERGE).

It is noted that for simplicity in the following description we describe sharing or not sharing of one context variable (e.g. for the first bit only). This means in the following description we often look at the simple case of signalling only the first bit for each inter prediction mode using the context variables, which is either 1 (a separate/independent context variable is used) or 0 (the bit is bypass CABAC coded or shares the same context variable with another inter prediction mode so there is no separate/independent one). It is understood that different variants of this and following embodiments are not limited thereto, and context variables for other bits, or indeed all bits, may be shared/not shared/bypass CABAC coded in the same way.

In a first variant of the eighteenth embodiment, all inter prediction modes available for use in the encoding or decoding process share at least some CABAC context(s).

In this variant, the index coding and its related parameters (e.g. number of (initial) candidates) for the inter prediction modes may be set to be the same or similar wherever possible/compatible. For example, to simplify their signalling the number of candidates for the AFFINE MERGE mode and for the MERGE mode is set to 5 and 6 respectively, the number of initial candidates for the MMVD MERGE mode is set to 2, and the maximum number of candidates is 40 for the TRIANGLE MERGE mode. And a TRIANGLE MERGE index is not signalled using an unary max code as in other inter prediction modes. For this TRIANGLE MERGE mode, context variable for only the first bit (for the TRIANGLE MERGE index) can be shared with the other inter prediction modes. An advantage of this variant is a simplification of the encoder and decoder design.

In a further variant, the CABAC contexts for indexes of all the Merge inter prediction modes are shared. This means that only one CABAC context variable is needed for the first bits of all the indexes. In a yet further variant, if an index contains more than one bit to be CABAC coded, the coding of the additional bits (all CABAC coded bits apart from the first bit) are treated as a separate part (i.e. as if it were for another syntax element as far as the CABAC coding process is concerned), and if more than one index has more than one bits to be CABAC coded, one same context variable is shared for these CABAC coded “additional” bits. An advantage of this variant is a reduction in the amount of CABAC contexts. This reduces the storage requirement for context states, which need to be stored at the encoder and the decoder side, without significantly impacting the coding efficiency for a large majority of sequences processed by a video codec implementing the variant.

FIG. 29 illustrates another further variant's decoding process for inter prediction modes. This figure is similar to FIG. 26, but it includes an implementation of this variant. In this figure, when the current CU is processed in the MMVD MERGE mode, its MMVD MERGE index is decoded as the same index (i.e. the “Merge index” (2919)) as the MERGE index of the regular MERGE mode, while taking into account that in the MMVD MERGE mode only 2 initial candidates are available for selection, not 6 as in the regular MERGE mode. As there are only 2 possibilities, this “shared” index used in the MMVD MERGE mode is essentially a flag. As the same index is shared, the CABAC context variable is the same for this flag in the MMVD MERGE mode and for the first bit of the MERGE index in the MERGE mode. Then, if it is determined that the current CU is to be processed in the MMVD MERGE mode (2925), the distance index (2911) and the direction index (2912) are decoded. If it is determined that the current CU is to be processed in the AFFINE MERGE mode (2914), its AFFINE MERGE index is decoded as the same index (i.e. the “Merge index” (2919)) as the MERGE index of the regular MERGE mode, while taking into account that in the AFFINE MERGE mode the maximum candidate number (i.e. the maximum index number) is 5, not 6 as in the regular MERGE mode. If it is determined that the current CU is to be processed in the TRIANGLE MERGE mode (2918), the first bit is decoded as the shared index (2919), and as a consequence the same CABAC context variable is shared with the regular MERGE mode. When this CU is processed in the TRIANGLE MERGE mode (2926), the remaining bits related to the TRIANGLE MERGE index are decoded (2923).

So e.g. during the CABAC coding process, when processing these indexes/flags, the number of separate (independent) context variable used for the first bit of the indexes/flags for each inter prediction mode is:

(Regular) MERGE=1; and

MHII=AFFINE MERGE=TRIANGLE=MMVD=0 (shared with Regular MERGE).

In a second variant, when one or both of the TRIANGLE MERGE mode or the MMVD MERGE mode is used (i.e. information about the motion information predictor selection for a current CU is processed/encoded/decoded in the relevant inter prediction mode), its/their index signalling shares a context variable with the index signalling for the MERGE mode. In this variant, the CABAC context of the TRIANGLE MERGE index and/or the CABAC context of the MMVD MERGE index/flag share the same CABAC context of the MERGE index (for the (regular) MERGE mode). This means that only one CABAC state is needed for at least these three modes.

In a further variant of the second variant, the CABAC context of the TRIANGLE MERGE index and/or the CABAC context of the MMVD MERGE index/flag share the same first CABAC context variable for the MERGE index, e.g. the same context variable for the first bit of the MERGE index.

So e.g. during the CABAC coding process, when processing these indexes/flags, the number of separate (independent) context variable used for the first bit of the indexes/flags is:

(Regular) MERGE=1;

MHII (if available for use)=AFFINE MERGE (if available for use)=0 (shared with Regular MERGE) or 1 depending on the implementation; and

TRIANGLE=MMVD=0 (shared with Regular MERGE).

In a yet further variant of the second variant, when more than one context variables are used for the TRIANGLE MERGE index CABAC coding/decoding or more than one context variables are used for the MMVD MERGE index CABAC coding/decoding, they can all be shared, or be shared at least in part wherever compatible, with more than one CABAC context variables used for the MERGE index CABAC coding/decoding.

An advantage of this second variant is a reduction in the amount of contexts needed to be stored and consequently the amount of states needed to be stored at the encoder and the decoder side without significantly impacting the coding efficiency for the large majority of sequences processed by a video codec implementing them.

In a third variant, when one or both of the TRIANGLE MERGE mode or the MMVD MERGE mode is used (i.e. information about the motion information predictor selection for a current CU is processed/encoded/decoded in the relevant inter prediction mode), its/their index signalling shares a context variable with the index signalling for the AFFINE MERGE mode. In this variant, the CABAC context of the TRIANGLE MERGE index and/or the CABAC context of the MMVD MERGE index/flag share the same CABAC context of the AFFINE MERGE index (for the AFFINE MERGE mode).

In a further variant of the third variant, the CABAC context of the TRIANGLE MERGE index and/or the CABAC context of the MMVD MERGE index/flag share the same first CABAC context variable for the AFFINE MERGE index, e.g. the same context variable for the first bit of the AFFINE MERGE index.

So e.g. during the CABAC coding process, when processing these indexes/flags, the number of separate (independent) context variable used for the first bit of the indexes/flags is:

(Regular) MERGE (if available for use)=0 (shared with AFFINE MERGE) or 1 depending on the implementation;

MHII (if available for use)=0 (shared with Regular MERGE);

AFFINE MERGE=1; and

TRIANGLE=MMVD=0 (shared with AFFINE MERGE).

In a yet further variant of the third variant, when more than one context variables are used for the TRIANGLE MERGE index CABAC coding/decoding or more than one context variables are used for the MMVD MERGE index CABAC coding/decoding, they can be all shared, or be shared at least in part wherever compatible, with more than one CABAC context variables used for the AFFINE MERGE index CABAC coding/decoding.

In a fourth variant, when the MMVD MERGE mode is used (i.e. information about the motion information predictor selection for a current CU is processed/encoded/decoded in the MMVD MERGE mode), its index signalling shares a context variable with the index signalling for the MERGE mode or the AFFINE MERGE mode. In this variant, the CABAC context of the MMVD MERGE index/flag is the same CABAC context of the MERGE index or the same CABAC context of the AFFINE MERGE index.

So e.g. during the CABAC coding process, when processing these indexes/flags, the number of separate (independent) context variable used for the first bit of the indexes/flags is:

(Regular) MERGE=1;

MHII (if available for use)=0 (shared with Regular MERGE);

AFFINE MERGE (if available for use)=0 (shared with Regular MERGE) or 1 depending on the implementation; and

MMVD=0 (shared with Regular MERGE).

OR

(Regular) MERGE (if available for use)=0 (shared with AFFINE MERGE) or 1 depending on the implementation;

MHII (if available for use)=0 (shared with Regular MERGE);

AFFINE MERGE=1; and

MMVD=0 (shared with AFFINE MERGE).

In a fifth variant, when the TRIANGLE MERGE mode is used (i.e. information about the motion information predictor selection for a current CU is processed/encoded/decoded in the TRIANGLE MERGE mode), its index signalling shares a context variable with the index signalling for the MERGE mode or the AFFINE MERGE mode. In this variant, the CABAC context of the TRIANGLE MERGE index is the same CABAC context of the MERGE index or the same CABAC context of the AFFINE MERGE index.

So e.g. during the CABAC coding process, when processing these indexes/flags, the number of separate (independent) context variable used for the first bit of the indexes/flags is:

(Regular) MERGE=1;

MHII (if available for use)=0 (shared with Regular MERGE);

AFFINE MERGE (if available for use)=0 (shared with Regular MERGE) or 1 depending on the implementation; and

TRIANGLE=0 (shared with Regular MERGE).

OR

(Regular) MERGE (if available for use)=0 (shared with AFFINE MERGE) or 1 depending on the implementation;

MHII (if available for use)=0 (shared with Regular MERGE);

AFFINE MERGE=1; and

TRIANGLE=0 (shared with AFFINE MERGE).

In a sixth variant, when the TRIANGLE MERGE mode is used (i.e. information about the motion information predictor selection for a current CU is processed/encoded/decoded in the TRIANGLE MERGE mode), its index signalling shares a context variable with the index signalling for the MMVD MERGE mode. In this variant, the CABAC context of the TRIANGLE MERGE index is the same CABAC context of the MMVD MERGE index. So e.g. during the CABAC coding process, when processing these indexes/flags, the number of separate (independent) context variable used for the first bit of the indexes/flags is:

MMVD=1;

TRIANGLE=0 (shared with MMVD); and

(Regular) MERGE or MHII or AFFINE MERGE=depends on the implementation and whether it is available for use or not.

In a seventh variant, when one or both of the TRIANGLE MERGE mode or the MMVD MERGE mode is used (i.e. information about the motion information predictor selection for a current CU is processed/encoded/decoded in the relevant inter prediction mode), its/their index signalling shares a context variable with the index signalling for an inter prediction mode which can include an ATMVP predictor candidate in its list of candidates, i.e. said inter prediction mode is capable of having an ATMVP predictor candidate as one of the available candidates. In this variant, the CABAC context of the TRIANGLE MERGE index and/or the MMVD MERGE index/flag share the same CABAC context of the index of the inter prediction mode that may use the ATMVP predictor.

In a further variant, the CABAC context variable for the TRIANGLE MERGE index and/or the MMVD MERGE index/flag share the same first CABAC context variable for the MERGE index of the MERGE mode with an includable ATMVP candidate or the AFFINE MERGE index of the AFFINE MERGE mode with an includable ATMVP candidate.

In a yet further variant, when more than one context variables are used for the TRIANGLE MERGE index CABAC coding/decoding or more than one context variables are used for the MMVD MERGE index CABAC coding/decoding, they can all be shared, or be shared at least in part wherever compatible, with more than one CABAC context variables used for the MERGE index of the MERGE mode or the AFFINE MERGE index of the AFFINE MERGE mode with an includable ATMVP candidate.

An advantage of these variants is a coding efficiency improvement because the ATMVP (predictor) candidate is a predictor that benefits most from the CABAC adaptation when compared with other types of predictors.

Nineteenth Embodiment

According to the nineteenth embodiment, one or both of the TRIANGLE MERGE mode or the MMVD MERGE mode is available for use in the encoding or decoding process, and an index/flag for one or both of these inter prediction modes is CABAC bypass coded when signalling the index/flag.

In a first variant of the nineteenth embodiment, all inter prediction modes available for use in the encoding or decoding process CABAC bypass code/decode its index/flag to signal the index/flag. In this variant, all indexes for all inter prediction modes are coded without using a CABAC context variable (e.g. by the bypass coding engine 1705 in FIG. 17). This means that all bits of the MERGE index (2619), the AFFINE MERGE index (2615), the MMVD MERGE index (2610), the TRIANGLE MERGE index (2623) from FIG. 26 are CABAC bypass coded. FIGS. 30(a)-30(c) illustrate coding of an index/flag according to this embodiment. FIG. 30(a) illustrates an MMVD MERGE index coding of an initial MMVD MERGE candidate. FIG. 30(b) illustrates a TRIANGLE MERGE index coding. FIG. 30(c) illustrates an AFFINE MERGE index coding, which can also be easily used for a MERGE index coding.

So e.g. during the CABAC coding process, when processing these indexes/flags, the number of separate (independent) context variable used for the indexes/flags is:

(Regular) MERGE (if available for use)=MHII (if available for use)=AFFINE MERGE (if available for use)=TRIANGLE (if available for use)=MMVD (if available for use)=0 (all bypass coded). An advantage of this variant is a reduction in the amount of contexts needed to be stored, and consequently the amount of states needed to be stored at the encoder and the decoder side with only a small impact on the coding efficiency for a large majority of sequences to be processed by a video codec implementing the variant. It is noted though that it could lead to a high loss when used in the screen content coding. This variant represents another compromise between the coding efficiency and complexity when compared to other variants/embodiments. The impact on the coding efficiency is often small. Indeed, with a large number of inter prediction modes available, an average amount of data needed to signal an index for each inter prediction mode is smaller than an average amount of data needed for signalling a MERGE index when only the MERGE mode is enabled/available for use (this comparison is for the same sequence and the same coding efficiency compromise). This means the CABAC coding/decoding's efficiency from adapting probabilities of bins based on a context may be less efficient.

In a second variant, when one or both of the TRIANGLE MERGE mode or the MMVD MERGE mode is used (i.e. information about the motion information predictor selection for a current CU is processed/encoded/decoded in the relevant inter prediction mode), its/their index/flag is signalled by CABAC bypass coding/decoding the index/flag. In this variant, the MMVD MERGE index and/or the TRIANGLE MERGE index are CABAC bypass coded. Depending on the implementation, i.e. if the MERGE mode and the AFFINE MERGE mode are available for use, the MERGE index and the AFFINE MERGE index have their own contexts. In a yet further variant, the context for MERGE index and the AFFINE MERGE index are shared.

So e.g. during the CABAC coding process, when processing these indexes/flags, the number of separate (independent) context variable used for the first bit of the indexes/flags is:

(Regular) MERGE=AFFINE MERGE=0 or 1 depending on the implementation;

MHII (if available for use)=0 (shared with the Regular MERGE); and

TRIANGLE=MMVD=0 (bypass coded).

An advantage of these variants is an improvement in the coding efficiency compared to the previous variant as they provide yet another compromise between the coding efficiency and the reduction of CABAC contexts. Indeed, the TRIANGLE MERGE mode is not often selected. Consequently, when its context is removed, i.e. the TRIANLGE MERGE mode uses CABAC bypass coding, the impact on the coding efficiency is small. Although the MMVD MERGE mode tends to be selected more often than the TRIANGLE MERGE mode, the probabilities of selecting the MMVD MERGE mode's first and second candidates tend to be more equal than for other inter prediction modes such as the MERGE more or the AFFINE MERGE mode so for the MMVD MERGE mode there is not as much benefit to be had from using the contexts of the CABAC coding. Another advantage of these variants is a small coding efficiency impact for screen content sequences as the most influential inter prediction mode for the screen content is the MERGE mode.

In a third variant, when the MERGE mode, the TRIANGLE MERGE mode or the MMVD MERGE mode is used (i.e. information about the motion information predictor selection for a current CU is processed/encoded/decoded in the relevant inter prediction mode), its/their index/flag is signalled by CABAC bypass coding/decoding the index/flag. In this variant, the MMVD MERGE index, the TRIANGLE MERGE index and the MERGE index are CABAC bypass coded. So e.g. during the CABAC coding process, when processing these indexes/flags, the number of separate (independent) context variable used for the first bit of the indexes/flags is:

(Regular) MERGE=TRIANGLE (if available for use)=MMVD (if available for use)=0 (bypass coded);

MHII (if available for use)=0 (same as the Regular MERGE); and

AFFINE MERGE=1.

This variant provides an alternative compromise compared to the other variants, e.g. this variant giving a larger coding efficiency decrease for screen content sequences than the previous variant.

In a fourth variant, when the AFFINE MERGE mode, the TRIANGLE MERGE mode or the MMVD MERGE mode is used (i.e. information about the motion information predictor selection for a current CU is processed/encoded/decoded in the relevant inter prediction mode), its/their index/flag is signalled by CABAC bypass coding/decoding the index/flag. In this variant, the AFFINE MERGE index, the MMVD MERGE index and the TRIANGLE MERGE index are CABAC bypass coded and the MERGE index is coded with one or more CABAC contexts. So e.g. during the CABAC coding process, when processing these indexes/flags, the number of separate (independent) context variable used for the first bit of the indexes/flags is:

(Regular) MERGE=1;

AFFINE MERGE=TRIANGLE (if available for use)=MMVD (if available for use)=0 (bypass coded); and

MHII (if available for use)=0 (shared with the Regular MERGE). An advantage of this variant compared to the previous one is a coding efficiency increase for screen content sequences.

In a fifth variant, inter prediction modes available for use in the encoding or decoding process CABAC bypass code/decode its index/flag to signal the index/flag, except when said inter prediction mode can include an ATMVP predictor candidate in its list of candidates, i.e. said inter prediction mode is capable of having an ATMVP predictor candidate as one of the available candidates. In this variant, all indexes of all inter prediction modes are CABAC bypass coded, except when the inter prediction mode is capable of having an ATMVP predictor candidate. So e.g. during the CABAC coding process, when processing these indexes/flags, the number of separate (independent) context variable used for the first bit of the indexes/flags is:

(Regular) MERGE with an includable ATMVP candidate=1;

AFFINE MERGE (if available for use)=TRIANGLE (if available for use)=MMVD (if available for use)=0 (bypass coded); and

MHII (if available for use)=1 (shared with the Regular MERGE) or 0 depending on the implementation,

OR

AFFINE MERGE with an includable ATMVP candidate=1;

(Regular) MERGE (if available for use)=TRIANGLE (if available for use)=MMVD (if available for use)=0 (bypass coded); and

MHII (if available for use)=0 (same as the Regular MERGE).

This variant also provides another complexity/coding efficiency compromise for a majority of natural sequences. It is noted though that for screen content sequences it may be preferable to have the ATMVP predictor candidate in the Regular MERGE candidates list.

In a sixth variant, inter prediction modes available for use in the encoding or decoding process CABAC bypass code/decode its index/flag to signal the index/flag when said inter prediction mode is not a SKIP mode (e.g. not one of the Regular MERGE Skip mode, AFFINE MERGE Skip mode, TRIANGLE MERGE Skip mode, or MMVD MERGE Skip mode). In this variant, all indexes are CABAC bypass coded for any CU which is not processed in a SKIP mode, i.e. is not skipped. The indexes for a skipped CU (i.e. a CU which is processed in a SKIP mode) may be processed using any one of the CABAC coding techniques described in relation to aforementioned embodiments/variants (e.g. only the first bit, or more than one bit, has a context variable, and the context variable may be shared or not shared).

FIG. 31 is a flow chart of a decoding process for inter prediction modes illustrating this variant. The process in FIG. 31 is similar to FIG. 29 except it has an additional “Skip mode” determination/check step (3127), after which the index/flag (“Merge_idx”) is decoded using either a context in CABAC decoding (3119) or CABAC bypass decoding (3128). It is understood that according to yet another variant, result of the determination/check made in previous steps CU is Skip (2902/3102), MMVD Skip (2908/3108), and CU is Skip (2916/3116) in FIG. 29 or FIG. 31 is used to make the “Skip mode” determination/check instead of the additional “Skip mode” determination/check step (3127).

This variant has a low impact on the coding efficiency because the SKIP modes are generally more frequently selected than the non-SKIP modes (i.e. non-Skip inter prediction modes such as Regular MERGE mode, MHII MERGE mode, AFFINE MERGE mode, TRIANGLE MERGE mode, or MMVD MERGE mode) and also because a selection of the first candidate is more likely for the SKIP modes than non-SKIP modes. SKIP modes are designed for a more predictable motion so their indexes should be more predictable as well. So probability exploiting CABAC coding/decoding is more likely to be useful for SKIP modes. However, non-SKIP modes are likely to be used when the motion is less predictable so a more random selection from the predictor candidates is more likely to occur. So for non-SKIP modes, CABAC coding/decoding is less likely to be efficient.

Twentieth Embodiment

According to the twentieth embodiment, data is provided in a bitstream, wherein said data is for determining whether an index/flag for one or more of the inter prediction modes is to be signalled by using: a CABAC bypass coding/decoding; a CABAC coding/decoding with separate context variable(s); or a CABAC coding/decoding with one or more shared context variable(s). For example, such said data may be a flag for enabling or disabling use of one or more independent context(s) for an inter prediction mode's index coding/decoding. Using such data, it is possible to control the use or disuse of the context sharing in the CABAC coding/decoding or the CABAC bypass coding/decoding.

In a variant of the twentieth embodiment, the CABAC context sharing between two or more indexes of two or more inter prediction modes depends on data transmitted in the bitstream, e.g. at a higher level than a CU level (e.g. at a level for an image portion larger than the smallest CU such as at a sequence, frame, slice, tile, or CTU level). For example, this data may indicate that, for any CU in a particular image portion, the CABAC context(s) of the MERGE index of the MERGE mode are to be shared (or not) with one or more other CABAC context(s) of another inter prediction mode.

In another variant, one or more index is CABAC bypass coded depending on data transmitted in the bitstream, e.g. at a higher level than a CU level (e.g. at a slice level). For example, this data may indicate that, for any CU in a particular image portion, an index of a particular inter prediction mode is to be CABAC bypass coded.

In a variant, to further improve coding efficiency, at the encoder side, the value of this data for indicating sharing of context(s) for, or CABAC bypass coding/decoding, an index of one or more of the inter prediction mode(s) can be selected based on how often the one or more inter prediction mode(s) is used in previously encoded frames. An alternative may be to select the value of this data based on the type of sequences to be processed or the type of application for which the variant is to be implemented.

An advantage of this embodiment is a controlled coding efficiency increase compared to the previous embodiments/variants.

Implementation of Embodiments of the Invention

One or more of the foregoing embodiments are implemented by the processor 311 of a processing device 300 in FIG. 3, or corresponding functional module(s)/unit(s) of the encoder 400 in FIG. 4, of the decoder 60 in FIG. 5, of the CABAC coder in FIG. 17 or a corresponding CABAC decoder thereof, which perform the method steps of the one or more foregoing embodiments.

FIG. 19 is a schematic block diagram of a computing device 2000 for implementation of one or more embodiments of the invention. The computing device 2000 may be a device such as a micro-computer, a workstation or a light portable device. The computing device 2000 comprises a communication bus connected to:—a central processing unit (CPU) 2001, such as a microprocessor;—a random access memory (RAM) 2002 for storing the executable code of the method of embodiments of the invention as well as the registers adapted to record variables and parameters necessary for implementing the method for encoding or decoding at least part of an image according to embodiments of the invention, the memory capacity thereof can be expanded by an optional RAM connected to an expansion port for example;—a read only memory (ROM) 2003 for storing computer programs for implementing embodiments of the invention;—a network interface (NET) 2004 is typically connected to a communication network over which digital data to be processed are transmitted or received. The network interface (NET) 2004 can be a single network interface, or composed of a set of different network interfaces (for instance wired and wireless interfaces, or different kinds of wired or wireless interfaces). Data packets are written to the network interface for transmission or are read from the network interface for reception under the control of the software application running in the CPU 2001;—a user interface (UI) 2005 may be used for receiving inputs from a user or to display information to a user;—a hard disk (HD) 2006 may be provided as a mass storage device;—an Input/Output module (IO) 2007 may be used for receiving/sending data from/to external devices such as a video source or display. The executable code may be stored either in the ROM 2003, on the HD 2006 or on a removable digital medium such as, for example a disk. According to a variant, the executable code of the programs can be received by means of a communication network, via the NET 2004, in order to be stored in one of the storage means of the communication device 2000, such as the HD 2006, before being executed. The CPU 2001 is adapted to control and direct the execution of the instructions or portions of software code of the program or programs according to embodiments of the invention, which instructions are stored in one of the aforementioned storage means. After powering on, the CPU 2001 is capable of executing instructions from main RAM memory 2002 relating to a software application after those instructions have been loaded from the program ROM 2003 or the HD 2006, for example. Such a software application, when executed by the CPU 2001, causes the steps of the method according to the invention to be performed.

It is also understood that according to another embodiment of the present invention, a decoder according to an aforementioned embodiment is provided in a user terminal such as a computer, a mobile phone (a cellular phone), a tablet or any other type of a device (e.g. a display apparatus) capable of providing/displaying a content to a user. According to yet another embodiment, an encoder according to an aforementioned embodiment is provided in an image capturing apparatus which also comprises a camera, a video camera or a network camera (e.g. a closed-circuit television or video surveillance camera) which captures and provides the content for the encoder to encode. Two such examples are provided below with reference to FIGS. 20 and 21.

FIG. 20 is a diagram illustrating a network camera system 2100 including a network camera 2102 and a client apparatus 2104.

The network camera 2102 includes an imaging unit 2106, an encoding unit 2108, a communication unit 2110, and a control unit 2112.

The network camera 2102 and the client apparatus 2104 are mutually connected to be able to communicate with each other via the network 200.

The imaging unit 2106 includes a lens and an image sensor (e.g., a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS)), and captures an image of an object and generates image data based on the image. This image can be a still image or a video image. The imaging unit may also comprise zooming means and/or panning means which are adapted to zoom or pan (either optically or digitally) respectfully.

The encoding unit 2108 encodes the image data by using said encoding methods explained in one or more of the foregoing embodiments. The encoding unit 2108 uses at least one of encoding methods explained in the foregoing embodiments. For another instance, the encoding unit 2108 can use a combination of encoding methods explained in the foregoing embodiments.

The communication unit 2110 of the network camera 2102 transmits the encoded image data encoded by the encoding unit 2108 to the client apparatus 2104. Further, the communication unit 2110 receives commands from client apparatus 2104. The commands include commands to set parameters for the encoding of the encoding unit 2108.

The control unit 2112 controls other units in the network camera 2102 in accordance with the commands received by the communication unit 2110.

The client apparatus 2104 includes a communication unit 2114, a decoding unit 2116, and a control unit 2118. The communication unit 2114 of the client apparatus 2104 transmits the commands to the network camera 2102. Further, the communication unit 2114 of the client apparatus 2104 receives the encoded image data from the network camera 2102.

The decoding unit 2116 decodes the encoded image data by using said decoding methods explained in one or more of the foregoing embodiments. For another instance, the decoding unit 2116 can use a combination of decoding methods explained in the foregoing embodiments.

The control unit 2118 of the client apparatus 2104 controls other units in the client apparatus 2104 in accordance with the user operation or commands received by the communication unit 2114. The control unit 2118 of the client apparatus 2104 controls a display apparatus 2120 so as to display an image decoded by the decoding unit 2116. The control unit 2118 of the client apparatus 2104 also controls a display apparatus 2120 so as to display GUI (Graphical User Interface) to designate values of the parameters for the network camera 2102 including the parameters for the encoding of the encoding unit 2108.

The control unit 2118 of the client apparatus 2104 also controls other units in the client apparatus 2104 in accordance with user operation input to the GUI displayed by the display apparatus 2120. The control unit 2118 of the client apparatus 2104 controls the communication unit 2114 of the client apparatus 2104 so as to transmit the commands to the network camera 2102 which designate values of the parameters for the network camera 2102, in accordance with the user operation input to the GUI displayed by the display apparatus 2120.

The network camera system 2100 may determine if the camera 2102 utilizes zoom or pan during the recording of video, and such information may be used when encoding a video stream as zooming or panning during filming may benefit from the use of affine mode which is well-suited to coding complex motion such as zooming, rotating and/or stretching (which may be side-effects of panning, in particular if the lens is a ‘fish eye’ lens).

FIG. 21 is a diagram illustrating a smart phone 2200.

The smart phone 2200 includes a communication unit 2202, a decoding/encoding unit 2204, a control unit 2206 and a display unit 2208.

The communication unit 2202 receives the encoded image data via network 200.

The decoding/encoding unit 2204 decodes the encoded image data received by the communication unit 2202. The decoding/encoding unit 2204 decodes the encoded image data by using said decoding methods explained in one or more of the foregoing embodiments. The decoding/encoding unit 2204 can use at least one of decoding methods explained in the foregoing embodiments. For another instance, the decoding/encoding unit 2204 can use a combination of decoding or encoding methods explained in the foregoing embodiments.

The control unit 2206 controls other units in the smart phone 2200 in accordance with a user operation or commands received by the communication unit 2202 or via an input unit. For example, the control unit 2206 controls a display apparatus 2208 so as to display an image decoded by the decoding unit 2204.

The smart phone may further comprise an image recording device 2210 (for example a digital camera and associated circuity) to record images or videos. Such recorded images or videos may be encoded by the decoding/encoding unit 2204 under instruction of the control unit 2206. The smart phone may further comprise sensors 2212 adapted to sense the orientation of the mobile device. Such sensors could include an accelerometer, gyroscope, compass, global positioning (GPS) unit or similar positional sensors. Such sensors 2212 can determine if the smart phone changes orientation and such information may be used when encoding a video stream as a change in orientation during filming may benefit from the use of affine mode which is well-suited to coding complex motion such as rotations.

Alternatives and Modifications

It will be appreciated that an object of the present invention is to ensure that affine mode is utilised in a most efficient manner, and certain examples discussed above relate to signalling the use of affine mode in dependence on a perceived likelihood of affine mode being useful. A further example of this may apply to encoders when it is known that complex motion (where an affine transform may be particularly efficient) is being encoded. Examples of such cases include:

a) A camera zooming in/out

b) A portable camera (e.g. a mobile phone) changing orientation during filming (i.e. a rotational movement)

c) A ‘fisheye’ lens camera panning (e.g. a stretching/distortion of a portion of the image

As such, an indication of complex motion may be raised during the recording process so that affine mode may be given a higher likelihood of being used for the slice, sequence of frames or indeed the entire video stream.

In a further example, affine mode may be given a higher likelihood of being used depending on a feature or functionality of the device used to record the video. For example, a mobile device may be more likely to change orientation than (say) a fixed security camera so affine mode may be more appropriate for encoding video from the former. Examples of features or functionality include: the presence/use of zooming means, the presence/use of a positional sensor, the presence/use of panning means, whether or not the device is portable, or a user-selection on the device.

While the present invention has been described with reference to embodiments, it is to be understood that the invention is not limited to the disclosed embodiments. It will be appreciated by those skilled in the art that various changes and modification might be made without departing from the scope of the invention, as defined in the appended claims. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and/or all of the steps of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features and/or steps are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features.

It is also understood that any result of comparison, determination, assessment, selection, execution, performing, or consideration described above, for example a selection made during an encoding or filtering process, may be indicated in or determinable/inferable from data in a bitstream, for example a flag or data indicative of the result, so that the indicated or determined/inferred result can be used in the processing instead of actually performing the comparison, determination, assessment, selection, execution, performing, or consideration, for example during a decoding process.

In the claims, the word “comprising” does not exclude other elements or steps, and the indefinite article “a” or “an” does not exclude a plurality. The mere fact that different features are recited in mutually different dependent claims does not indicate that a combination of these features cannot be advantageously used.

Reference numerals appearing in the claims are by way of illustration only and shall have no limiting effect on the scope of the claims.

In the preceding embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over, as one or more instructions or code, a computer-readable medium and executed by a hardware-based processing unit.

Computer-readable media may include computer-readable storage media, which corresponds to a tangible medium such as data storage media, or communication media including any medium that facilitates transfer of a computer program from one place to another, e.g., according to a communication protocol. In this manner, computer-readable media generally may correspond to (1) tangible computer-readable storage media which is non-transitory or (2) a communication medium such as a signal or carrier wave. Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, code and/or data structures for implementation of the techniques described in this disclosure. A computer program product may include a computer-readable medium.

By way of example, and not limitation, such computer-readable storage media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, or other magnetic storage devices, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if instructions are transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. It should be understood, however, that computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transient media, but are instead directed to non-transient, tangible storage media. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

Instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, application specific integrated circuits (ASICs), field programmable gate/logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Accordingly, the term “processor,” as used herein may refer to any of the foregoing structure or any other structure suitable for implementation of the techniques described herein. In addition, in some aspects, the functionality described herein may be provided within dedicated hardware and/or software modules configured for encoding and decoding, or incorporated in a combined codec. Also, the techniques could be fully implemented in one or more circuits or logic elements. 

1. A method of encoding information about a motion information predictor, comprising: selecting one of a plurality of motion information predictor candidates; and encoding information for identifying the selected motion information predictor candidate using CABAC coding, wherein for the CABAC coding of at least one bit of said information, a Merge mode, in which a block predictor is obtained from a first block predictor and a second block predictor divided by a boundary, uses the same context variable as another inter prediction mode that is not said Merge mode, wherein the boundary is filtered between the first and second block predictor.
 2. A method of decoding information about a motion information predictor, comprising: decoding information for identifying one of a plurality of motion information predictor candidates using CABAC decoding; and using the decoded information to select the one of the plurality of motion information predictor candidates, wherein for the CABAC decoding of at least one bit of said information, a Merge mode, in which a block predictor is obtained from a first block predictor and a second block predictor divided by a boundary, uses the same context variable as another inter prediction mode that is not said Merge mode, wherein the boundary is filtered between the first and second block predictor.
 3. The method of claim 1, wherein all bits except for a first bit of the information are bypass CABAC coded.
 4. The method of claim 1, wherein the another inter prediction mode comprises one or both of a Merge mode or Merge mode for Affine motion prediction.
 5. The method of claim 1, wherein the another inter prediction mode comprises a Merge mode which uses as a block predictor an average of an intra block predictor and a predictor based on a regular Merge mode.
 6. The method of claim 1, wherein the plurality of motion information predictor candidates for the another inter prediction mode comprises a candidate for collocated temporal subblock prediction.
 7. (canceled)
 8. The method of claim 1, wherein at least one bit of said information is CABAC coded when a Skip mode is used. 9-20. (canceled)
 21. The method of claim 1, wherein said information comprises a motion information predictor index or a flag.
 22. The method of claim 1, wherein a motion information predictor candidate comprises information for obtaining a motion vector.
 23. The method of claim 2, further comprising obtaining, from a bitstream, information for indicating use of one of the Merge mode in which a block predictor is obtained from a first block predictor and a second block predictor divided by a boundary, an MMVD Merge mode, another Merge mode, a Merge mode for Affine motion information prediction, or a Merge mode which uses as a block predictor an average of an intra block predictor and a predictor associated with a regular Merge mode.
 24. The method of claim 2, further comprising obtaining, from a bitstream, information for determining a maximum number of motion information predictor candidates includable in the plurality of motion information predictor candidates.
 25. A device for encoding information about a motion information predictor comprising: means for selecting one of a plurality of motion information predictor candidates; and means for encoding information for identifying the selected motion information predictor candidate using CABAC coding, wherein for the CABAC coding of at least one bit of said information, a Merge mode, in which a block predictor is obtained from a first block predictor and a second block predictor divided by a boundary, uses the same context variable as another inter prediction mode that is not said Merge mode, wherein the boundary is filtered between the first and second block predictor.
 26. A device for decoding information about a motion information predictor, comprising: means for decoding information for identifying one of a plurality of motion information predictor candidates using CABAC decoding; and means for using the decoded information to select the one of the plurality of motion information predictor candidates, wherein for the CABAC decoding of at least one bit of said information, a Merge mode, in which a block predictor is obtained from a first block predictor and a second block predictor divided by a boundary, uses the same context variable as another inter prediction mode that is not said Merge mode, wherein the boundary is filtered between the first and second block predictor. 27-29. (canceled)
 30. A non-transitory computer-readable carrier medium storing a program which, when executed by one or more processors, causes the one or more processors to perform a method of encoding information about a motion information predictor, the method comprising: selecting one of a plurality of motion information predictor candidates; and encoding information for identifying the selected motion information predictor candidates using CABAC coding, wherein for the CABAC coding of at least one bit of said information, a Merge mode, in which a block predictor is obtained from a first block predictor and a second block predictor divided by a boundary, uses the same context variable as another inter prediction mode that is not said Merge mode, wherein the boundary is filtered between the first and second block predictor.
 31. A non-transitory computer-readable carrier medium storing a program which, when executed by one or more processors, causes the one or more processors to perform a method of decoding information about a motion information predictor, the method comprising: decoding information for identifying one of a plurality of motion information predictor candidates using CABAC decoding; and using the decoded information to select the one of the plurality of motion information predictor candidates, wherein for the CABAC decoding of at least one bit of said information, a Merge mode, in which a block predictor is obtained from a first block predictor and a second block predictor divided by a boundary, uses the same context variable as another inter prediction mode that is not said Merge mode, wherein the boundary is filtered between the first and second block predictor.
 32. The method of claim 2, wherein all the bits except for a first bit of the information are bypass CABAC decoded.
 33. The method of claim 2, wherein the another inter prediction mode comprises one or both of a Merge mode or a Merge mode for Affine motion prediction.
 34. The method of claim 2, wherein the another inter prediction mode comprises a Merge mode which uses as a block predictor an average of an intra block predictor and a predictor based on a regular Merge mode.
 35. The method of claim 2, wherein the plurality of motion information predictor candidates for the another inter prediction mode comprises candidate for collocated temporal subblock prediction.
 36. The method of claim 2, wherein at least one bit of said information is CABAC decoded when a Skip mode is used.
 37. The method of claim 2, wherein said information comprises a motion information predictor index or a flag.
 38. The method of claim 2, wherein a motion information predictor candidate comprises information for obtaining a motion vector.
 39. The method of claim 3, further comprising obtaining, from a bitstream, information for indicating use of one of the Merge mode in which a block predictor is obtained from a first block predictor and a second block predictor divided by a boundary, an MMVD Merge mode, another Merge mode, a Merge mode for Affine motion information prediction, or a Merge mode which uses as a block predictor an average of an intra block predictor and a predictor associated with a regular Merge mode.
 40. The method of claim 3, further comprising obtaining, from a bitstream, information for determining a maximum number of motion information predictor candidates includable in the plurality of motion information predictor candidates. 